Why are iPhone apps prettier than Android apps?

by Ryan Beesley » Mon, 07 Dec 2009 14:04:09 GMT

Sponsored Links
 Consistent UI means that there is a more gradual learning curve for someone to 
use an unfamiliar app.  There's a reason that Wordstar edit commands are still 
being used for applications today, rr the familiarity of vi and emacs commands. 
 It was also one of the driving factors in Windows 3.x adoption.

When you do something to break the common and familiar metaphors in software, 
you had better have a benchmark application that developers will be mimicing 
for years to come.  Unless you're writing the next Office or Photoshop, you 
will have better convergience if you keep to a standard look and feel that the 
user will instantly grasp.

Bryce may have been beautiful to look at, but functionally it was very 
difficult to pick up and use.


-----Original Message-----
From: admin.androidsl...@googlemail.com 
Sent: Friday, December 04, 2009 3:43 AM
To: Android Discuss
Subject: [android-discuss] Re: Why are iPhone apps prettier than Android apps?

Users expectations seem to be lower on UI aspects too.

In app ratings, users tend to ask for features rather than a better
looking UI.

Sometimes users will complain if an app doesn't use the native Android
UI. Not sure why, I don't think every app should look the same!


Other Threads

1. halo, salam kenal

Dear all and mod,

Perkenankan saya anggota baru utk gabung...
Nama : octoryza putra
Lokasi : makassar

Mohon bimbingan dari para senior utk belajar android.

Rencana mau pake spica, yg lagi otw ke makassar :)


"Indonesian Android Community [id-android]" 

2. Serious Problem with AudioRecord on NexusOne

Hey. I'm running AudioRecord to capture sound. It runs inside a
service. But, after the initial run after installing the app (in which
I've never seen this bug occur), the sound goes blank about 20% of the
time after 0-20 seconds of running. Audio data STILL gets captured
from the hardware, however, it is completely silent. If you examine
the console you will see that AudioHardwareQSD enters standby mode,
or  you can use the volume meter and you will see that it goes dead to
assist in seeing this bug.

05-30 11:49:37.639: DEBUG/dalvikvm(697): GC_FOR_MALLOC freed 8417
objects / 326880 bytes in 62ms
05-30 11:49:37.639: INFO/AudioHardwareQSD(59): do input routing device
05-30 11:49:37.639: INFO/AudioHardwareQSD(59): Routing audio to
05-30 11:49:37.650: WARN/AudioFlinger(59): RecordThread: buffer
05-30 11:49:37.780: DEBUG/AudioHardwareQSD(59): Switching audio device
05-30 11:49:37.780: DEBUG/AudioHardwareQSD(59): Speakerphone
05-30 11:49:37.871: INFO/AudioHardwareQSD(59): AudioHardware PCM
record is going to standby.

This bug does not occur on any other phone than the nexus. Someone
told me that AudioHardwareQSD is
related to the snapdragon audioprocessor for the second microphone.

Quickly view the relevant source in pastebin: http://pastebin.com/3xVEjiLE

The full source is here:

Which is part this bug: http://code.google.com/p/android/issues/detail?id=8732



3. Any other way to point to R.java?

4. Asynchronous Http Request

5. Clear defaults programmatically

6. Google Feedback fo Android

7. nullPointerException with custom ArrayAdapter