107 karma · joined August 6, 2010
But take someone who is building a great product, and who has the experience for building the company around the product, and you've got a better combination than just a first-timer with a product.
Comparative advantage is huge here. Yes, you could probably fill out all the business incorporation paperwork, write all the copy,etc,etc - but having another person do that work lets you focus on your primary skill.
Biggest thing for me working w/non-programmers? They keep me focused on building features that are useful to users. They still applaud the non-noticeable things like a sweet Hadoop cluster I built but the overall focus on product is key.
I've tackled these issues personally, and at my company (iPad app). Keep in mind that your users will demand that your app at least feel native, if not the same UI controls. You think that you'll have the freedom to run on each platform, but in reality you'll be dealing with the quirks of each platform and that will set you back some dev time. Webkit is not 100% the same on each browser
What Phonegap gives you is a demarcation point to drop in your HTML code - and that's it. If you need API access for accelerometer, vibrate, etc then Phonegap can help. If your app is focused more on the user experience, then Phonegap cannot help you.
Do you really want to launch an app that will feel awkward on every platform, or just develop a native app for each major platform? That platform space isn't as large as you might think - iOS, Android, <pick your consumer markets third>
I'm a mobile product manager by day, my contact info is in my profile if you have any more questions.
I hope to see JQM support this without a lot of fiddling. It would be killer to have an app that was essentially PhoneGap + JQM UI + loading of JQM-compliant pages. No XML request, parsing, mapping to UI elements needed.