Phonegap - alternatives? Go native?

wezcountry

New member
Aug 31, 2009
1,788
22
0
In the EUSSR
Hi I have a project for a phone app, which needs to be deployed on iOS, Android and Windows phone. It's a relatively simple app (connect to mySQL and uses jquery mobile) and for the sake of speed and simplicity I am planning on using phonegap.

However there are a couple of problems with phonegap including the licensing - as far as I can tell you can only have 25 phonegap build projects per account - I am aiming to ship this to more clients than that, and each needs his own version of the app. The client then gives the app to their contacts. I can't see a way to manage on-going development, bug fixing etc while using phonegap.

I don't mind paying for services, can anyone recommend an alternative that they have used? I've had a look around but nothing strikes me as being as good.

I have considered going native and developing the app without using phonegap. I deffo would not want to learn more than one language, is it possible to develop for the three main platforms using a single language (C# maybe?). It would be a hill to climb in terms of time though maybe a good investment in the long run.

Thanks for any advice.
 


Why does each client need their own version? That sounds like an absolute nightmare.

Can't you change the design around as needed, so there's white label functionality that runs off instructions it gets from a central database of clients / licenses? One app, put a license ID# in a config file, and call up instructions from a license database about who the client is, and how the app should function.

Up to you, but that sounds a whole lot better to me than maintaining 25+ versions of virtually the same thing. So when there's a bug or feature upgrade, you have to modify, recompile, and release 25+ versions?
 
Why does each client need their own version? That sounds like an absolute nightmare.

Can't you change the design around as needed, so there's white label functionality that runs off instructions it gets from a central database of clients / licenses? One app, put a license ID# in a config file, and call up instructions from a license database about who the client is, and how the app should function.

Up to you, but that sounds a whole lot better to me than maintaining 25+ versions of virtually the same thing. So when there's a bug or feature upgrade, you have to modify, recompile, and release 25+ versions?

Thanks and I totally agree with the last paragraph - it's stalled me for a few days.

I need to figure-out how the client can give his workers his specific version of the app (with his data). Would it be possible for a client to send his workers the app plus a config file (i.e. containing the license ID#)?
 
Are you accessing mysql directly over the network? If so, is it secured? Are you sure? Could that mysql user delete all your data?
 
Are you accessing mysql directly over the network? If so, is it secured? Are you sure? Could that mysql user delete all your data?

Yeah, it would be as secured as every other mysql app we're developing.

Once the framework, technical strategy etc has been figured-out, building it is the easy part.