Very exciting now as the debates and discussions and research and information gathering (to ascertain and finalise our best marketing strategy in terms of what functions the free app will have and what functions the paid app will have) are finally nearing an end.
the next move is to incorporate those decisions and move forward, which means finalising development and making that phone app talk to the web app and vice versa, then test it in real life scenarios before moving toward launching on itunes.
On another note, it is also exciting that, if numbers and sales go well and interest is high enough, we may look toward developing it as a multi platform supported business with delivery on android and blackberry platforms. It is also interesting that Apple have a media event planned for January 27 to launch the new iPhone OS4.0 and much rumoured tablet, delivery on this device could be a straight forward port if it uses much the same code and frameworks as the phone.
2010 could be an exciting year folks!
Tuesday, 19 January 2010
Tuesday, 12 January 2010
different apps and functionality
so we are at the point where we decide how to approach the launch of the app. Do we have a free app with annual subscription? do we have a paid app with annual subscription?
We need the annual subscription as the software will archive upto 12 months of estimates and invoices on our servers. Do we just charge for the app and have no subscriptions?
Apple SDK states it can utilise in-app subscriptions. Do we make use of this (and let apple have 30%) or do we have an online webapp subscription payment module?
There is a ton of questions regarding this and we are knocking it about at the moment. Perhaps we have a free app and no paid app but with only annual subscriptions to gain the full functionality, even then, do we make this subscription payment online or in-app?
This is the point we are at right now and it seems to be a very lengthy point that doesnt seem to be moving forward at any great rate. The only good news is, once we settle on it, we will start to move fast!
We need the annual subscription as the software will archive upto 12 months of estimates and invoices on our servers. Do we just charge for the app and have no subscriptions?
Apple SDK states it can utilise in-app subscriptions. Do we make use of this (and let apple have 30%) or do we have an online webapp subscription payment module?
There is a ton of questions regarding this and we are knocking it about at the moment. Perhaps we have a free app and no paid app but with only annual subscriptions to gain the full functionality, even then, do we make this subscription payment online or in-app?
This is the point we are at right now and it seems to be a very lengthy point that doesnt seem to be moving forward at any great rate. The only good news is, once we settle on it, we will start to move fast!
Subscribe to:
Posts (Atom)
