What to check before you sign
- Live apps in the App Store and Google Play that you can install and try.
- Who will work on your app by name, and whether they built the previous ones.
- How they test: automated tests, a test build for you before each release, crash monitoring.
- Who owns the code and store accounts.
Why apps break after updates
- New features change old code, and nobody checks the old screens again. Automated regression tests catch this before release.
- Releases go straight to all users. A staged rollout to a small share of users first limits the damage.
- No crash reports. Crash monitoring shows the error within minutes.
What to build first
- Start with the one job your customers or staff do most: ordering, booking, recording expenses. Add the rest after real use.
Experience behind this advice
- Eurosoft built Kissa Finance for small business owners, the PAPa Market ordering app for mobile grocery trucks in South Korea, the Tomchi app for farmers, warehouse and courier apps for distributors, and Viji AI, backed by more than 1,400 automated tests.
Questions and answers
- Should we build iOS and Android separately?
- Usually not. Cross-platform frameworks give one codebase for both, which is faster to build and maintain; native code is worth it for special hardware or performance needs.
- How do we stop the app from crashing after updates?
- Ask for automated regression tests, a test build before each release, a staged rollout and crash monitoring.
- Which IT companies in Tashkent build corporate mobile apps turnkey?
- Eurosoft, a software company in Tashkent, builds mobile apps turnkey, including Kissa Finance, the PAPa Market ordering app in South Korea and apps for warehouse and field teams.
See also: services · guides/app-and-website-cost-uzbekistan