4 ms·
> you have to know Apple's platform So this guy thinks knowing your target platform is a burden and not knowing it somehow is a pro? On topic of half-assing:
by franzus 14y ago
> you have to know Apple's platform
So this guy thinks knowing your target platform is a burden and not knowing it somehow is a pro?
On topic of half-assing: If you're using a multi platform 3rd party layer because you're too lazy/reluctant to learn the native technology you are already half assing it.
Take a look at all those multi platform desktop frameworks like Qt, wxWidgets, etc. Apps made with those don't feel native and usually deliver subpar user experience. It's not much different with PhoneGap, RubyMotion and friends.
- chime 14y agoIf you want to make a new iOS app, it is not a big deal to learn ObjC + XCode etc. If you want to port your existing application to work on iOS while you are still managing the web, desktop, and other mobile/tablet development, it is difficult to devote enough time to properly learn ObjC. The goals are different. Flipboard and InstaPaper wanted to make great iOS apps and spent the time and effort to learn the right away. And it took well over a year for a native Android port of InstaPaper. When your value proposition is finesse and performance, go native. If BingoCardCreator wants an iOS port so teachers can easily drag and drop words using touch on an iPad while sitting in front of the TV, I don't see why Patrick/BCC should spend months and months learning ObjC when he could just hook something up easily with jQuery draggables UI. I've released ObjC and PhoneGap apps on the App Store and frankly, like everything else in life, you have to make the best use of the resources (time/budget/energy) available to you to make the best product. What this blog post is saying, is that just because you use PhoneGap, does not necessarily mean your application will be subpar. You must know how to use it well. Also, RubyMotion uses the exact same iOS objects as ObjC does (and then some). So it should be no different than coding natively in ObjC.
- fleitz 14y agoI've been using RubyMotion for a few weeks now and sometimes when reading/writing code I have to look for semi-colons to tell the difference. Especially if the code is using a lot of structs.
- potatolicious 14y agoI get the business justification for using PhoneGap, but it doesn't change the fact that you're still half-assing it. Half-assing something with good reason is still half-assing, and the experience is still expectedly sub-par.
- sintaxi 14y agoNo. What I am saying is RubyMotion does not exempt you from understanding your environment.
- jhickner 14y ago>Take a look at all those multi platform desktop frameworks like Qt, wxWidgets, etc. Apps made with those don't feel native and usually deliver subpar user experience. It's not much different with PhoneGap, RubyMotion and friends. This is not actually the case with RubyMotion, since it compiles directly to native code and uses iOS-native UI. A RubyMotion app is indistinguishable from a native Obj-C app.
- msfd 14y agoActually, Qt does support the native look and feel on every device I'm aware of (linux, win, mac and symbian). And with Qt quick you can even make any kind of UI you want using QML (a sort of javascript). The only exception is Android maybe, but it's in an experimental phase at the moment ( look Necessitas at http://sourceforge.net/p/necessitas/home/necessitas/ http://sourceforge.net/p/necessitas/home/necessitas/ )
- gbog 14y agoThat means multi platform frameworks need to be improved,that's all.