{"content":{"sharePage":{"page":0,"digests":[{"id":"48946473","dateCreated":"1326128622","smartDate":"Jan 9, 2012","userCreated":{"username":"treubank","url":"https:\/\/www.wikispaces.com\/user\/view\/treubank","imageUrl":"https:\/\/www.wikispaces.com\/user\/pic\/1313243275\/treubank-lg.jpg"},"monitored":false,"locked":false,"links":{"self":"https:\/\/vetapp.wikispaces.com\/share\/view\/48946473"},"dateDigested":1532129204,"startDate":null,"sharedType":"discussion","title":"Developer Comments","description":"This idea of picking tools is very complex and usually comes down to developer preference. Here are some comments from other developers that may help fill in the gaps for some of us and will also demonstrate that there is much debate even among the developers themselves...
\n
\n1.
\nPhonegap
\nSencha
\nAppcelerator Titanium
\n
\nI develop native apps using native code AND I developer native apps using HTML5-wrapped bridges using Phonegap.
\n
\nWhen you are doing low level bitmap manipulation or need to create and OpenGL view, you go native. When you need to "checkin" or pull down content from the web and populate a UI, you go HTML5-wrapped native. It's that simple.
\n
\n2.
\n1) Sencha is an HTML5 framework to create mobile web apps.
\n2) Titanium and Phonegap work as wrappers that run your code in different platforms (think Java VM). It is not an HTML5 framework. They are native apps.
\n
\n3.
\nYou're absolutely correct. There is *no* viable cross-platform native mobile app development tool set. The key word is viable. Sure there's stuff out there that you can waste a bunch of time with.
\n
\n4.
\nYou can take a WebView and slap it into a regular native shell and you have a "native" app which is really just a web app - which is pretty much what Netflix did for the iPad.
\n5.
\nChoosing the platform for building your application is of critical importance. Native applications are very expensive and if you are developing for RIM, expect that to double. If you decide to go with an HTML5 application, make sure you have a strategy for dealing with offline devices and application distribution. That is where the hybrid model becomes useful.","replyPages":[{"page":0,"digests":[],"more":0}]}],"more":false},"comments":[]},"http":{"code":200,"status":"OK"},"redirectUrl":null,"javascript":null,"notices":{"warning":[],"error":[],"info":[],"success":[]}}