Docstoc

Android vs. iPhone- Developer Considerations

Chris Hawkins, Founder & CEO of SignNow (signnow.com), discusses Android vs Iphone Developer considerations. Find out the differences on the development end.

  1. For iPhone, focus on design and aestetic to be competitive
  2. Minimize rick and fragmentation when building Android apps
  3. Plan for structured releases with iPhone apps
  4. Release quickly and liberally with Android apps
  5. iPhone apps follow a structured flow for delivery
  6. Android apps are inconsistent
  7. Android apps allow customization of the interface through widgets

There is many differences between the iPhone and Android in terms of development.

Just a couple of things, first on the iPhone, because the marketplace is so competitive now, probably more competitive in many ways you really have to focus on maximizing the beauty of your app. Spend a lot of time on design. Otherwise, there is no way you are going to stand out above the pack.

With Android, it is a little bit different though. You have to build your app in such a way that with all the variety of devices and sizes that it is going to be on, that you have the low risk of your app failing to work. And if you overdesign it to some degree, you could run into issues. With iPhone, you really can’t spend too much time on that.

iPhone, because of the lag time which we found to be anywhere up to two weeks, I think you really have that structured releases. You have to be very careful what you release into the wild because you might have a long time before you were able to replace it. You can not iterate quite as fast. So if you use more of the traditional old school development psycho with it if you will.

But Android, you can release about as quickly as you can on the web. I probably still would recommend you know doing it quite as fast as maybe you might on web, you know, many times a day release. But that said, you can be much more liberal with your releases.

On the iPhone, I would say apps should follow this very standard flow. Apple has done a recently good job of -- in most cases, figuring out the right way to go through something.

But on Android, you can have a lot more flexibility. One, because the apps themselves are very inconsistent so you might want to make a trade-off and do what is best for your app even if it is different and then also leverage widgets.

The widgets that can go on to your homepage can be a really cool tool and people build great apps around just having great widgets for you to use.

So in summary, there is a different sets of pros and cons and things to consider on each platform. On a high-level iPhone you really got to go with beauty and consistency. And with Android, you got to try to minimize your risk of things going wrong on the different devices.