StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POIPhone over Android and vice versa
text
Body
copied!<p>I develop applications on both <strong>IPhone</strong> and <strong>Android</strong>. As a part of my organization's <em>Technical Session</em> program I have myself delivering the next session on <strong>IPhone or Android</strong>. Getting the session made me start comparing both technologies, which believe me, is really a tough job. As a programmer in both technologies I often think how will the <em>Application</em> seem to be if I used the other one. Which further makes me list out pron and cons of both.<br> <strong>Android a ahead of IPhone</strong>:<br> There are couple of factors where <strong>Android</strong> steps ahead of <strong>IPhone</strong>. </p> <ul> <li><p>Multiple apps at same time </p></li> <li><p>Information visible on home screen </p></li> <li><p>Better notifications </p></li> <li><p>Hardware flexibility </p></li> </ul> <p><strong>IPhone ahead of Android</strong>:<br> Following are the factors: </p> <ul> <li><p>UI Smoothness and Consistency </p></li> <li><p>Language support </p></li> <li><p>Accessibility options </p></li> <li><p>Battery life </p></li> <li><p>Resource efficiency </p></li> <li><p>Hardware quality </p></li> <li><p>Better App Store </p></li> </ul> <p>However, as a programmer, I want my session to be more of <em>technical</em> rather than a being a general overview of both technologies. For which I need some help. For instance <strong>Android's</strong> memory management is way ahead of that of <strong>IPhone's</strong>. On the other hand <strong>IPhone's</strong> <em>UI</em> has no comparison at all.<br> What more points(technical) can I include in my session. Also, kindly correct me if I am wrong somewhere above. </p> <p>Nitish </p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload