5 ms·
Even granted that, the reason Apple doesn't want that is still because of the UX. Apps with the same codebase for Android/iPhone will automatically suck as far
by ptomato 17y ago
Even granted that, the reason Apple doesn't want that is still because of the UX. Apps with the same codebase for Android/iPhone will automatically suck as far as the UI is concerned. Things like the lack of multitouch gestures on android, different screen sizes, &c. Certainly has never worked well on desktop platforms... see: Java UI toolkits, QT (which looks fairly native but tends to feel very wrong), Adobe Air, &c.
- tumult 17y agoWho cares what you think they want? Read the developer agreement. What's it say? Anything that isn't C, C++, or Objective-C is banned.
- ptomato 17y agoYup. And your point is? For the third time now, my point isn't that this is a good thing, and I'm certainly not a fan of the decision. My point is that Apple isn't doing this because they hate developers, or want to tweak Adobe's nose (well, maybe a little), but because all they care about is their product's user experience.
- tumult 17y agoWhy does it matter what language I used to develop an application, if it produces a binary that runs acceptably on the platform and otherwise follows all of the rules? I can write a more stable application in SML, Haskell or even untyped Scheme than most of the clowns I see making app store junk in Objective-C.
- rortian 17y agoApple does not allow third party apps to use multitouch so that is a known issue. >Apps with the same codebase for Android/iPhone will automatically suck as far as the UI is concerned Hardly. There is the graphics api called opengl that works on both iPhone and Android (and your ps3 and computer).