A Note on Implementation and Design Choices

Some might ask themselves why we decided to rewrite and develop a separate WordPress Admin in close parallel to what is being done in the WP core, instead of simply re-skinning the standard output to seemingly achieve the same goal.

Although the above statement is in itself not entirely accurate given our thorough adherence to the WordPress Admin API and development guidelines wherever possible, the answer can be summed up in two word: universal access.

Because we’ve committed to support the widest array of platforms possible right from the beginning (from iPhone to braille readers), based on the overwhelming feedback from the original wp-hackers thread that instigated this project, things such as low memory specs, slow processors and networks, common lack of server-side scripting, countless navigation and usability paradigms and so on truly defined the core of our design choices when it comes to both WPhone’s back and front ends. The fact of the matter is that these elements are not a focus of the standard WP Admin, nor should they entirely be (although accessibility has always been an important part of the WP core team’s efforts).

Will these decisions pay off for us personally in the competition context? I’m not sure; both contestant apps are pretty neat tools. But what we’re sure of is that it’ll pay off for our user base, and is ultimately the most important to us. :o)

Get a Trackback link

1 Comments

  1. Stephane Daury October 25, 2007

    I didn’t want to add a link to my personal blog in the body of the post itself, but if you’re interested in the more technical aspect of mobile web development, you can also check out a related opinion post on the subject I wrote at http://tekartist.org/blog/2007/10/25/apples-new-iphone-developer-center/

Leave a comment