[nfbcs] FW: compiling iPhone apps to Android apps

[Jorge A. Paez]

haha--yes, my friend tried to give me a whole lecture on why I need to
go back to Apple--I left Apple about a year ago and switched back  to
Windows.
Anyway, yes that's interesting.
However, the flexibility with Android I think will eventually make it
more appealing then developing in Apple's closed architecture, unless
you have a specific reason to do that, such as services that appeal
specifically to that demographic range, particularly in terms of the
finance or luxury industry, because, as common statistics state, the
IOS owners tend to be wealthier and more inclined to spend money, most
likely because there is no high-end Android phone, and no Windows
phone for that matter, that can compete at that level yet.
Also,Apple appeals more to those who want a finished package and who
don't want to worry about anything relating to the actual system.
Its more of a pick up, turn on and run device, with the user not
having to worry about much, though I suspect a lot of that feel comes
from branding and GUI/UX design.
I for one, will stick to developing for Windows, Linux and Android
once I get started, as developing in a closed-end architecture isn't
interesting for me.
Also--its not just closed-end in the sense of consumers, bbut any
programmer who wants to do anything, even if its just a 1-shot project
for someone, will have to buy a mac and I fine that fact extremely
annoying.


On 3/25/15, Joseph C. Lininger via nfbcs <nfbcs at nfbnet.org> wrote:
> The article makes some good points, specifically the thing about
> cross-platform development and the use of different development
> environments. It's not always a straight forward problem. I don't
> develop mobile apps, but I've written code that I wanted to run on, say,
> Linux and Windows for instance and even simple software can present a
> challenge there.
>
> It makes another good point though, at the very beginning of the
> article, although it tries to gloss over it. Without going into actual
> numbers which are certain to be wrong anyway, I'll just say that
> excluding either the Android or the Apple community severely limits the
> audience for your app. Perhaps in the case of the NFB app specifically,
> it doesn't matter that much since I've noticed most of the NFB members I
> know use an apple device. However, in the general case that's not a
> guarantee. In fact, it's not even a garantee in the blind community. I'm
> not part of the federation, but I am a blind mobile user. I carry an
> Android device myself, and have no interest in changing devices.
>
> As an interesting side note, some of the Apple users I know can get
> downright annoying about trying to talk me into switching smart phones
> and/or buying a MAC. (It's something that happens with both blind and
> sighted people) It's gotten bad enough I've had to start preempting
> people by saying "not interested", more or less politely, when they
> first get started. Makes people mad, but saves me at least 10 minutes
> worth of time that I don't have to spend pretending to listen. LOL
> Joe
>
> _______________________________________________
> nfbcs mailing list
> nfbcs at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for
> nfbcs:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/jorgeapaez1994%40gmail.com
>


-- 
Thank you.




Jorge A. Paez

LinkedIn: http://www.linkedin.com/in/jorgeapaez

Elance page: http://jorgeapaez1994.elance.com