Think of foursquare or quora as a product. I know they are completely different, but the dynamics are Similar. Crowdsourced social applications that require user input and participation.
In view of this, should the “product” be a mobile application, a website, or a combination of both? Did most ideas first become websites, and mobile apps an afterthought? Is the mobile app just a companion or the whole experience?
The most important thing is how to make this decision before development? Is there some kind of touchstone to determine which 3 options are effective?
Any tips, suggestions or guidance are very much appreciated.
Using native apps, you can get some advantages. You can usually create a richer experience, more powerful offline support (if applicable), widgets, etc. But this flexibility It takes a cost, an important one, and one you will pay again and again. If you can create a pure online version of the product, then you will be able to support a wider range of mobile phones more easily and will not prevent you from building native applications in the future Program. Starting with the application, as your main access method, you really created a lot of upfront work for yourself. Start with plan A and supplement with the application, unless there is a good reason not to do so.
div>
I’m in the planning and design phase of an idea.
Imagine foursquare or quora as a product, I know they are completely different, but the dynamics are similar . Crowdsourced social applications that require user input and participation.
In view of this, should the “product” be a mobile application, a website, or a combination of both? Did most ideas first become websites, and mobile apps an afterthought? Is the mobile app just a companion or the whole experience?
The most important thing is how to make this decision before development? Is there some kind of touchstone to determine which 3 options are effective?
Any hints, suggestions or guidance are greatly appreciated.
It is difficult to create a great mobile app. Now, do it twice , To support Android and iOS. But wait, are you going to support Blackberry? What happens once you go outside of the United States? What about Windows Phone?
Using native apps, you can get some advantages. You can usually create a richer experience, more powerful offline support (if applicable), widgets, etc. But this flexibility It takes a cost, an important one, and one you will pay again and again. If you can create a pure online version of the product, then you will be able to support a wider range of mobile phones more easily and will not prevent you from building native applications in the future Program. Starting with the application, as your main access method, you really created a lot of upfront work for yourself. Start with plan A and use the application to supplement, unless there is a good reason not to do so.
p>