|
|
|
|
|
|
by black_blood
3465 days ago
|
|
|
2nd dependency, Facebook deciding that the app violates their intent, I never thought it. If Facebook in fact does that, I don't think I can do anything about it. 1st dependency, dependency on mobile devices, yeah, I regret starting with the mobile app. Though this is a hybrid app, considering the time that I can spend on this and my pace, I might take nearly a month to make a web app. And now, I am not sure if I should go ahead and release the Android version, or work on the web app and release web app first. Any suggestions? |
|
|
As a general observation, many successful apps have a website in addition to a presence in the app stores. So it makes sense to assume you'll be building a web page anyway. For an app like yours, it's probably easier to test and iterate core logic on a webpage than in a mobile device.
Whether it makes sense to build a web page at this point requires looking at the risk of the second dependency versus the cost of building a page and that's a business decision for your business.
[1]: http://venturebeat.com/2013/06/26/get-to-no-as-fast-as-you-c...