Shipping a good mobile app is not just about writing code. A lot of time goes into building, testing on devices, chasing crashes and getting releases through the app stores. The right tools remove much of that friction. This is the toolkit we use and recommend, grouped by the job each tool does.
Key takeaways
- Use an AI coding assistant for boilerplate, tests and refactors, and review everything it writes.
- Pick one cross-platform framework, React Native with Expo or Flutter, and invest in its tooling.
- Install crash reporting and performance monitoring before your first public release.
- Automate a few end-to-end tests of your most important flows with Maestro or Detox.
- Automate builds, signing and store submissions so releases are routine, not risky.
1. AI coding assistants
AI coding assistants are now a normal part of development. They are useful for:
- Generating boilerplate such as screens, forms, API clients and type definitions.
- Writing first drafts of unit tests and test data.
- Explaining unfamiliar code and native error messages.
- Refactoring repetitive code across many files.
They are much less reliable at platform-specific details: native module configuration, app store policies and subtle performance issues. Treat suggestions like a pull request from a new team member. Review them, run them on a real device and keep your linting and type checks strict so mistakes are caught early. Never paste secrets, keys or private customer data into an assistant your company has not approved.
2. A cross-platform framework with strong tooling
For most business apps, a cross-platform framework lets one team ship Android and iOS from a single codebase.
React Native with Expo is a strong default for teams that already know React and TypeScript. Expo provides:
- A development build workflow, so you can test native features on real devices quickly.
- Config plugins for native settings, which avoids editing native project files by hand for common needs.
- Over-the-air updates for JavaScript-only fixes, within the app stores' rules.
- EAS Build and EAS Submit for cloud builds and store submissions.
npx create-expo-app@latest my-app
cd my-app
npx expo start
Flutter is a good choice when you want pixel-identical UI across platforms and are happy to work in Dart. Its hot reload and widget inspector make UI work fast.
Native development with Android Studio (Kotlin) and Xcode (Swift) is still the right call for apps that depend heavily on platform-specific features. Even with a cross-platform framework, you will use both IDEs for debugging native issues, profiling and simulators.
If you are deciding between options, our guide to mobile app development services explains how we choose for each project.
3. Debugging and profiling
Fast feedback while developing saves hours every week.
- React Native DevTools and the Expo dev menu: inspect components, view logs and debug JavaScript.
- Flutter DevTools: inspect widgets, profile frame rendering and track memory.
- Android Studio profilers and Xcode Instruments: find CPU, memory and battery problems that only show up in native code.
- Network inspection tools such as Proxyman or Charles: see exactly what your app sends and receives, which helps debug API issues.
Profile on a mid-range Android phone, not only on the latest iPhone. Many of your users will be on older or lower-powered devices.
4. Crash reporting and performance monitoring
You cannot fix crashes you do not know about. Add a crash reporter before release:
- Firebase Crashlytics: free, widely used, and easy to set up if you already use Firebase.
- Sentry: crash and error reporting with performance tracing, release health and source maps for JavaScript stack traces.
Upload source maps or debug symbols with every build so stack traces point to your real code. Tag every event with the app version and track crash-free sessions per release, so you can spot a bad release quickly and roll back or ship a fix.
5. Automated testing
A small number of reliable tests beats a large, flaky test suite.
- Unit tests with Jest (React Native) or the Flutter test framework for business logic, formatting and state.
- Component tests with React Native Testing Library to check screens render and respond correctly.
- End-to-end tests with Maestro (simple YAML flows that drive the real app) or Detox (gray-box E2E testing for React Native).
# maestro/login.yaml
appId: com.example.app
---
- launchApp
- tapOn: "Email"
- inputText: "test@example.com"
- tapOn: "Password"
- inputText: "correct-horse"
- tapOn: "Log in"
- assertVisible: "Welcome"
Start with E2E tests for the flows that make money or would cause the most support tickets: sign-up, login, checkout and payments.
6. CI/CD and release automation
Manual builds and store uploads are slow and error-prone. Automate them:
- EAS Build and EAS Submit for Expo projects: cloud builds for both platforms, managed signing credentials and automated submission.
- fastlane: a long-standing open-source tool for automating builds, screenshots and store uploads for native and cross-platform apps.
- GitHub Actions, Bitrise or Codemagic: run linting, type checks and tests on every pull request, and trigger builds on merges.
A simple pipeline: every pull request runs lint, type check and unit tests; merges to the main branch produce an internal test build (TestFlight and Play internal testing); tagged releases go to the stores. Read more in our DevOps and CI/CD services.
7. Collaboration tools
Good apps come from teams that share context easily:
- Figma for designs, with Dev Mode for exact spacing, colours and assets.
- A shared issue tracker such as Linear, Jira or GitHub Issues, linked to pull requests.
- Storybook for React Native or a widget catalogue for Flutter, so designers and developers can review components in isolation.
How to adopt these tools without slowing down
- Add crash reporting first. It gives the fastest return.
- Automate builds and internal test distribution next.
- Add E2E tests for your two or three most important flows.
- Roll out an approved AI assistant with clear rules on review and data.
- Review the setup every few months and remove tools nobody uses.
Frequently asked questions
What are the best tools for mobile app development?
The best toolkit combines a cross-platform framework such as React Native with Expo or Flutter, an AI coding assistant, a crash reporter like Firebase Crashlytics or Sentry, an end-to-end testing tool such as Maestro or Detox, and automated builds with EAS Build, fastlane or a CI service. Android Studio and Xcode remain essential for native debugging.
Should I choose React Native or Flutter for a new app?
Choose React Native with Expo if your team knows React and TypeScript or you want to share code and skills with a web app. Choose Flutter if you prefer Dart and want identical rendering across platforms. Both can build high-quality production apps, so team experience and existing code usually matter more than the framework itself.
Is Expo good enough for production apps?
Yes, Expo is widely used for production React Native apps. Development builds and config plugins let you use most native libraries, EAS handles cloud builds and store submissions, and over-the-air updates speed up JavaScript fixes. Apps with unusual native requirements may still need custom native code, which Expo also supports.
Are AI coding assistants useful for mobile development?
AI coding assistants are useful for boilerplate, tests, explanations and repetitive refactors in mobile projects. They are less reliable for native configuration, store policies and performance tuning, so every suggestion should be reviewed and tested on real devices. Keep secrets and private customer data out of prompts unless the tool is approved by your company.
Which is better for crash reporting, Crashlytics or Sentry?
Firebase Crashlytics is free and simple, making it a good choice if your app already uses Firebase. Sentry adds performance tracing, release health and strong JavaScript source map support, which suits React Native teams that want deeper error context. Either works well if you upload symbols or source maps with every build.
How do I test a React Native app end to end?
Use Maestro or Detox to drive the real app on an emulator or device and check key user flows. Maestro uses simple YAML files and works with many frameworks, while Detox is built for React Native with tight synchronisation. Start with sign-up, login and checkout, and run the tests in CI on every release build.
How can I automate mobile app releases?
Set up a CI pipeline that runs tests on every pull request and builds signed apps automatically. Expo projects can use EAS Build and EAS Submit, while any project can use fastlane with GitHub Actions, Bitrise or Codemagic. Send each build to TestFlight and Google Play internal testing before promoting it to production.
Planning a mobile app?
Twigo builds Android and iOS apps with React Native and modern tooling, from first MVPs to full production apps. Explore our mobile app development services.
