Minuses:
● Need a card for payment and duns
● the necessary other legal entity
● We need a “disguise” of the application
● If the brand is popular, the application is quickly blocked
● scammers can use this method to steal data, since it is difficult to confirm the official origin of the application
Pros:
● gain access to the AppStore audience
● No need to re-profile and rebuild the work of iOS-commandmits
Lemaikin: “The company creates a separate account in another jurisdiction, copies the code of its application with another Bundle ID, with a different name, under other initials. But the problem is the same: the application is easy to track. Everything that goes to the App Store goes on a roar from Apple. I do not think that they will just miss the application – an analogue of a European company that has fallen under sanctions, the code of which is 99.99 % coincides. This is all easily tug around Apple, and your alternative account can be covered. Which happened before our eyes with large European banks. ”
Negative scenarios should be prepared now
Anton Kazenyuk: “We believe that we must prepare for a negative scenario now. Think about how to diversify the team, try to develop new skills from the developers. It is possible to go a little aside from the iOS development, so that in the case of the most negative scenario you can switch to another stack. There are different diversification options: cross platforms (Kotlin Multiplatform, Scade), back on SWIFT. You can “saw” applications for other regions if your company operates in several countries. You can go into the development of PWA applications. Or do not go far from Swift and make backend on it (Vapor, Ketura, Perfect), etc.
What path you choose depends on what kind of team you have, what skills it has, what more tasks, applications and what development plans you have.
If the rollback occurs, it doesn’t matter, soft or not soft – we can quickly return back. For example, if the App Store is blocked completely, everyone will be blocked by iOS development, iOS developers will have to retrain. In the event of a rollback, the lion’s share of the market will receive the one who will have a team and examination – and he will have time to publish his application faster.
We believe that in the current situation the team must be kept, but the risks of diversified. ”
What will happen to Android development
With Android development, everything is not so sad. There is AOSP (Android Open Source Project)
AOSP (Android Open Source Project) is an open source operating system, supported by Google. Since the source code is open, anyone can freely view and make the code and corrections to the project repository, although Google oversees its general direction and the main part of the development.
AOSP is not supplied with a set of Google applications, such as the Chrome browser, YouTube and Google Play Store. It also does not include a number of hidden Google APIs, which provide functions such as mobile payments, voice commands and cloud storage. They are licensed separately as Google Mobile Services (GMS).
For example, when Huawei lost access to American technologies, she could no longer license GMS, but could continue to use AOSP. Thus, Huawei began to replace GMS functions with its own Huawei Mobile Services.
That is why we believe that Android developers can calmly engage in my work and not twitch.
What will happen to the storage
Anton Kazenyuk: “If there are no problems with Android development, then in the situation with the storage they can arise. They can block the Eastern Europe, or maybe Google. At the moment, there are no serious players in Europe (except for Huawei-, Samsung-, Xiaomi-Stors), this market is open. Look at China, where there are hundreds of stakes and a giant Android audience. And if a negative scenario with the main stages works, the question arises where the audience is pouring, where the traffic is pouring, who will take this market. ”
The second aspect is the time of the students (which, of course, is paid by the company). A total of 18 people took the course, and at the start it seemed like a pretty risky investment. Especially when you remember that our main goal is simply to tell colleagues how their decisions affect the work of the developer, and vice versa.
We wanted to show the “underside” to all the guys from the production who are not personally connected with the code. So that everyone on the team understands how the mobile application works and why it works the way it does. They can answer these questions for themselves only by making their own projects and writing more than one line of code. We set out to be a great product team and have never regretted the hours we invested.
Difficulties
The main obstacle on the way to a successful final was not at all sudden phone calls (although there were many of them). Due to the difference in the initial level, the course program had to be redrawn more than once on the go. Because of this, the whole month was like walking a tightrope with a constant balance between explaining the simplest concepts and the desire to give as much material as possible.
While the first half of the thread is desperately trying to remember the difference between a variable and a constant, the other half can get bored. To keep the attention of each participant, I had to change the course plan, add explanatory screenshots, and literally look for new analogies on the go for easy memorization.
The technical side of the course also turned out to be more difficult than it seemed at first glance. Unlike Figma, using Xcode together with a group of ten people is simply impossible. The result is unforeseen errors like “I clicked on the wrong place and everything hung”. They also had to be solved on the fly.