How to understand mobile app development milestones?

Question

Project management

I work as a PM in a small company, now I'm changing jobs, almost all employers require an understanding of mobile development so that decomposed tasks can be correctly identified between conditional ios and android developers (direct speech from hr).
The question is, is the development process very different from the web, where we plan the architecture, write the back-front and cover it with all sorts of APIs? Perhaps someone can share articles on this topic, which describes the entire process of developing a mobile application.

Answer 1

It remains almost everything the same, it is added:

• uploading the application to the markets, taking into account any internal testing and constantly changing rules of the sites (literally in January, the rules for apple and android changed, which led to the inability to quickly correct the changes for the demonstration)
  
• more thorough planning (you already immediately lay down that on average it takes 2 weeks to lay out the application, and therefore demonstrate the changes, the same designs and pictures must be agreed in advance, obtain copyright confirmation for the content, since you can’t change it quickly), hence the need testers
  
• when designing, you need to give as much as possible from the server, again due to the previous points with the inability to quickly edit on the platform (for example, you may receive a complaint about the absence of the "rules of use" page, and if you do not give it back from the server, you will again have to wait two weeks)
  
• marketing functionality in markets is added (and this is filling texts, pictures, just promotion)
  
• one more channel for receiving applications in the form of reviews in the markets is being added, your claims service should be ready for this
  
• the delivery of works is carried out taking into account three platforms (that is, the API server and the admin panel, iOS and Android), this must be taken into account in the program and test methodology, laid in the gravity
  
• the need for three relatively independent development departments (there are no full stacks here, a separate backend / api server, iOS, Android)
  
• the approach is changing when working with cartography (you have to take into account the tariff policies of the underlying and functional providers)
  
• you need to agree on the shore, in whose name the account will be registered in the markets, it may take a long time to register accounts for your customer
  

From what is facilitated, in the absence of a web portal:

1. no SEO needed
   
2. no need for large high-quality images
   
3. less computing resource required (no bots), but again, predictability in response is required
   

Answer 2

A mobile application is also a front-end, but on mobile devices with its own operating system.
Therefore, this application interacts with the back in the same way and appropriate restrictions are imposed on it.
But there are much more advantages - access to the camera, geolocation, sensors, sensors, and more ...
But!
In some cases, a mobile application can be considered as a backend-independent application without Internet access. And you don't have to do it. It may not show itself at all on the outside.
Then it will look more like a non-desktop one.