How to manage mobile development?

Question

Project management

Good afternoon everyone! I recently started my job as a project manager in an outsourcing company and was assigned to develop native mobile applications. We use Scrum on the project. Recently, I thought that such a methodology is quite cumbersome for mobile applications, because:
1) teams are not cross-functional. Rarely, when an android programmer can fully replace ios or a backend developer, such developers work in parallel on their pieces. Testers and designers also work within their competencies.
2) a mobile application is created by 1-2 developers for one platform, if there is a ready-made API. And it turns out that there is one manager for one programmer.
3) the design is done separately from the team and refined already in the development process
4) very often, when developing mobile applications, they refuse to cover the code with tests, manual testing is done by developers in the process of work. The tester essentially duplicates this work.
I described my thoughts when working on relatively small projects (up to 3 months). I would like to hear the opinion of the projects that led mobile development: how the processes are built in your company, what frameworks and methodologies are used.

Answer 1

teams are not cross-functional
And this is normal, and even good. In our company, in the same way, there is a division of back, front and mobile workers of 2-4 people each for ios and android.
We also do design separately from development, but together with analytics.
Regarding the tests, the developers of the mp people are lazy, they can add a button on the TK, but they don’t even click on it (maybe this is the case with us), but the tester never duplicates this work. He will press, and will not press, and will see what he sends, and how he sends, and so on and so forth.
I did not understand about one manager for one programmer . Do you mean project team? When do you have your team?
Our mobile operators work on scrum. First, the requirements of the stakeholder are collected, then the PM or the analyst (if it’s a difficult refinement) write a specification for evaluation, according to this approximate specification, the mobile workers give an assessment, I throw time on top of all sorts of inconsistencies and roll out the cost to the customer, if he agrees, then the task moves either to analytics for complete TOR, or gets into the backlog, if "TK for assessment" is enough for work. Well, then, like everywhere else, a rally, a sprint is formed according to priorities, the task gets into it or not (since there are 30+ large clients), it is done. If the task is difficult, go to the testers. If it’s simple, a test assembly is going to the same uber that the support pokes (something elementary like move / remove the block and / or so on), and if everything is ok, access is given to the client, Which also confirms that everything is OK and then the assembly is laid out in the store or the market. If it's simple, then something like that.