As someone working on a phonegap project, I'd really advise against committing to this framework for mobile app development. It is good for really quick and dirty proof of concept things for devices, but for fully fledged mobile apps on iOS and android, there is an enormous gap in terms of performance. In order to get performance at least on par with native, you'd have to sacrifice TONS in terms of user experience.<p>Want gestures? You'll have to look towards things like iScroll and hammer.js, which work "sometimes". Add that to framework issues, and momentum based scrolling that you will have to implement yourself numerous times... Oh boy. Basically, things that come out of the box on native will have to be manually implemented by yourself, and none of these solutions will even come close to native experiences.<p>Add this to the fact that phonegap documentation is all over the place, and all you will get are senseless headaches. Save yourself the frustration of hacking the web into a mobile device and go native all the way. You will thank your self later.
I've been working on putting my PhoneGap/Famo.us knowledge into a consumable form. I hope this "playbook" (with the sample apps and examples) can be useful some folks who are building apps! It is still a WIP on both the copy and code ends, but I'll be adding improvements consistently.
Anyone done any comparisons of PG/Famo.us with Ionic (<a href="http://ionicframework.com/" rel="nofollow">http://ionicframework.com/</a>)? Seems Ionic is making a really strong case for hybrid app viability
Kind of sad the state PhoneGap push support is in. I checked the links and they have an if else for two completely different code branches for Android or iOS and don't support anything else:
<a href="http://www.practicalguidetomobileapps.com/resources/book/full_app/device_readyjs.html" rel="nofollow">http://www.practicalguidetomobileapps.com/resources/book/ful...</a><p>Ideally you would support more platforms and not have to make any distinction in the JavaScript and could have a single code path. Right now I pay Pushwhoosh a hefty fee per month for exactly that.<p>I hate working with closed source stuff that I can't bug fix and improve myself. Just the current state as evidenced by this guide is so far behind commercial offerings it would take months just to get it even comparable.
Just downloaded the book! Thanks for making it free. You are very generous!
I am looking to build a quick and dirty prototype for Tinder for X, and this is a great starting point for me. Thanks Nick!
I'm still confused as to why I'd want to use famo.us over an open source UI framework. From these screenshots it doesn't even look particularly good.
Feedback on <a href="http://www.practicalguidetomobileapps.com/resources/book/phonegap_and_cordova/phonegap_build.html" rel="nofollow">http://www.practicalguidetomobileapps.com/resources/book/pho...</a><p>3. don't see [New App] button
5. Broken URL (missing ".git")
6. "App must be less than 20 MB" (I'm on the Free Plan, I assume like most)
Does anyone know if there is a PG like tool which will help me make an app for camping/hiking routes? As in it's mostly a map, with some filters and it finds nearby locations.<p>Been looking around but it goes from "learn to code' straight to 'map technology' to 'map access api' which combines to be pretty darn hard.<p>Cheers
Come on people, HTML5 is winning! Another awesome and seemingly overlooked option here is ludei.com with their Cocoon platform, launcher and cloud build service. Put that together with React/Flux and some soon to be released Famous-React for flavour and its all possible. Then top it off with Webpack and your laughing.
This looks great! I've been wanting to get into mobile dev but stuck between choosing one of C#, Java, or Objective-C. I work with Javascript every day so this should be more familiar.