Jump to Navigation

Me on Twitter

  • SimpleDateFormat 'Z' pattern (RFC822) does not match XSD timezone (ISO8601). There's only a ':' differing and that makes a BIG difference ! 11 years 27 weeks ago
  • RT @vogella: I donate money to Ubuntu for...being amazing http://t.co/ESHrRbbh 11 years 27 weeks ago
  • @louistouzet Android : optimisation des performances 1 - Fluidité de l'interface via @objetdirect http://t.co/ZDkvA867 11 years 27 weeks ago
  • Another cup of #scala : it looks like #java. Enhanced. 11 years 27 weeks ago
  • Really fun game : @BadPiggies ! 11 years 28 weeks ago
  • Mailing from phone : so one can write a mail sms-style! 11 years 28 weeks ago
  • Second cup of #Scala : looks like mathematics 11 years 28 weeks ago
  • @CedN :-) 11 years 29 weeks ago
  • @mathieudulac "The class is designed to be self-contained" "You should have at least one year programming experience." https://t.co/cWBn2m0g 11 years 29 weeks ago
  • @CedN Ayé. 1er devoir terminé. Et toi ? 11 years 29 weeks ago

Small devices are ignored

This has been annoying me since the beginning : small screen devices are not taken into account by the vast majority of apps editors.

Worse : despite Google's pleading about size-caring (see http://developer.android.com/design), they recommend patterns that actually don't fit the real small screens for which size-caring IS important.
Example : the "action bar" and other icon bars : there is no place for such bars on small screens...

Of course the developer is able to adapt the GUI depending on the size of the screen, but if Google does not make it clear then I fear the battle is already lost...

 

Here are screenshots of Android Market and Google Reader on an Xperia Mini (HVGA 320x480, 88mm long) :

Android Market on Xperia MiniGoogle Reader on Xperia Mini

On the left screenshot : buttons zones are not clearly defined and the zoom button is too small, making it difficult to finger-tap them on small screen. Furthermore, one can only see 2 applications from the list (there was a screenful of it in the previous version)...

On the right screenshot : the user is swiping by mistake to the next article because the content is too large for the screen... Ooops too late ! If you swipe back to the previous article you'll have to scroll down again to where you were (this happens to me all the time...).

 

Another damage of device fragmentation...

 

Related links

Comments

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • E-Mail addresses are hidden with reCAPTCHA Mailhide.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>, <drupal5>, <drupal6>, <java>, <javascript>, <php>, <python>. The supported tag styles are: <foo>, [foo].
  • Twitter-style #hashtags are linked to search.twitter.com.

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.