Author

Topic: Web API in mobile app or mobile app with web surface? (Read 371 times)

hero member
Activity: 1204
Merit: 531
Metaverse 👾 Cyberweapons
I think a lot of it depends on the application and how people are intended to use it. I see a lot of services and apps that start out as web applications and end up with a mobile component. As an example, if your coding a business application dealing with data entry, you would probably want to start with a web version. A mobile version might give you other functionality, but the majority of the app is in the web version.

Thank you for your input! Yes, with your opinion and others added, I will create a web application first. From design, it will be mobile responsive and later -if deadline lets me- release a mobile app with some extra functionality. In this priority-order.

With this and since deadline makes me start from now on, I consider this discussion closed.
legendary
Activity: 1512
Merit: 1054
SpacePirate.io
I think a lot of it depends on the application and how people are intended to use it. I see a lot of services and apps that start out as web applications and end up with a mobile component. As an example, if your coding a business application dealing with data entry, you would probably want to start with a web version. A mobile version might give you other functionality, but the majority of the app is in the web version.
hero member
Activity: 1204
Merit: 531
Metaverse 👾 Cyberweapons
So, We had THIS discussion, which came to the conclusion both web applications and mobile applications are in demand and you should not really choose between them.

Now, the conclusion came to a choice. I think, I will have to develop both a mobile friendly web application and a mobile application with online features. The choice is, should I integrate the web application's feature in the mobile app (via an API) OR provide the mobile apps features in the web application (via a browser surface)?

What should take the PRIORITY in design?
Jump to: