Jump to Navigation

Me on Twitter

  • @ak_anneka Je découvre ton travail : c'est génial et ça donne envie d'en avoir un chez soi ! 24 weeks 15 hours ago
  • RT @ak_anneka: Je l'ai terminé ! I did it, I did it, yeah! #art #ink #artist #bird #tiny #objects #doodle #fun #color #red #yellow #ooak ht… 24 weeks 16 hours ago
  • RT @Devoxx: 26 weeks 1 day ago
  • RT @esa: Our week in #space images, featuring an Earth view taken by @Astro_Alex on the Space Station, the #Aeolus satellite's Vega rocket… 26 weeks 6 days ago
  • Wow.... Huge reservoir of liquid water detected under the surface of Mars https://t.co/PsJpjY7uFC via @AAAS @EurekAlert 30 weeks 3 days ago
  • RT @ChromiumDev: 30 weeks 3 days ago
  • RT @rupl: 31 weeks 2 days ago
  • Sorry @instapaper I can't wait any longer for you to be back online for Europeans. I'm back to @Pocket 36 weeks 5 days ago
  • Today it's #aiparis. Let's See that... 36 weeks 5 days ago
  • RT @MKBHD: Confirmed: You learn WAY more outside your comfort zone than in it. 37 weeks 6 days 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.