In short

Rui Codex builds Flutter apps for Android and iOS from one Dart codebase, with an ASP.NET Core or Appwrite back end where the app needs one. We publish our own Flutter apps and games on Google Play, several of them also on the App Store, and run their store releases and localisation ourselves.

We work on site in Belgium and the Benelux and deliver projects remotely across Europe, including Germany, Austria, Switzerland and France, in English, Dutch, French, German or Turkish, with the GDPR applied to all work.

We also build and publish our own mobile apps and games. See our apps and games

Does This Sound Like Your Business?

These are the problems an app project usually runs into, and most of them start after the code is written.

Two apps, twice the work

A separate Android app and iOS app means two codebases to build, test and maintain, and features that reach one platform months after the other.

An app that never reaches the store

The app works on a developer's phone, but signing, store listings, review rules and data-safety forms keep the release from going out.

Crashes you learn about from reviews

Without crash reporting, the first sign of a problem is a one-star review, and nobody can see on which device or in which version it happened.

Nobody maintains it after launch

New Android and iOS versions, store requirements and library updates arrive every year, and an app that is not kept up to date stops working on new devices or is no longer offered to new users.

One Codebase, Two Stores, Run Like a Product

Flutter compiles one Dart codebase into native apps for Android and iOS. We plan the app, its back end and its release process together, so the first store release is a routine step rather than a separate project at the end.

We publish our own apps and games built in Flutter on Google Play, several of them also on the App Store. The testing tracks and the localisation we use for them are the ones we set up for your app, together with crash reporting through Sentry.

34
Flutter apps and games we publish on Google Play
6
Of them also on the App Store
100%
Your source code, signing keys and store accounts
12+
Years of engineering experience (founder)

Key Capabilities

Everything from the first screen to an app that stays healthy in both stores.

  • Cross-Platform Apps in Flutter

    One Dart codebase for Android and iOS, with native code only where a feature needs it, such as the Android keyboard in our AI Mic Keyboard app, written in Kotlin.

  • Back Ends for Your App

    Accounts, sync, leaderboards and cloud backup on an ASP.NET Core API with SQL Server, or on a self-hosted Appwrite, of the kind that runs behind our own apps.

  • Store Releases

    Signing, store listings, data-safety and privacy forms, internal and closed testing tracks and staged production rollouts on Google Play, and TestFlight builds for the App Store.

  • Crash Reporting and Fixes

    Sentry crash and error reporting in every release, so a crash arrives with its stack trace, app version and device, and the fix ships in the next update rather than after the reviews.

  • Localisation

    Interfaces prepared for several languages from the start, right-to-left layouts included, and store listings per language. Many of our own apps ship with 11 interface languages; LetsLearn's interface covers 12, including right-to-left Arabic.

  • Offline-First and On-Device Data

    Local storage with SQLite, Drift or Hive, so the app keeps working without a connection and syncs when it returns, and data that should stay on the phone stays there.

How We Work

From the first conversation to an app that is live, monitored and updated.

  1. 1

    Scope

    We agree who the users are, what the first version must do, which platforms it targets and what it needs from a back end.

  2. 2

    Design

    Screens, navigation and data are designed together, and we decide what runs on the phone and what runs on the server.

  3. 3

    Build

    We build in short iterations and share test builds on real devices, so you use the app from the first weeks rather than at the end.

  4. 4

    Release

    We prepare the store listings and forms, test through the stores' own testing tracks and release to production in stages.

  5. 5

    Maintain

    Crash reports, new Android and iOS versions, store requirements and new features ship as regular updates.

Real-World Use Cases

The kinds of apps we build in Flutter, with examples from the apps we publish ourselves.

  • Customer App for an Existing Service

    An Android and iOS app in front of a service your customers already use, with sign-in, notifications and an API to your existing system.

  • Field and Staff App

    An app for people who work away from a desk: forms, photos and checklists that are saved offline and synchronised when the connection returns.

  • Learning and Content App

    Lessons, audio and progress tracking in several languages, as in our LetsLearn app, whose cards carry audio pronunciation and whose interface is localised into 12 languages.

  • Mobile Games

    Casual and puzzle games on the Flame engine with offline play, leaderboards and in-app purchases, like the games we publish on Google Play.

  • AI Features in an App

    Image, speech or text features that call an AI model through your own back end, such as the background removal in our PixelCut Pro app.

  • Taking Over an Existing Flutter App

    An app someone else built that needs fixes, a Flutter upgrade or a store release: reviewed first, then maintained and released by us.

Technology We Use

The frameworks and services our published Flutter apps are built on, chosen per project with you.

Flutter Dart Flame Riverpod BLoC SQLite / Drift Hive Kotlin ASP.NET Core SQL Server Appwrite (self-hosted) Firebase Cloud Messaging Google Play Billing RevenueCat Sentry

Each app in the list below uses a part of this stack. The full stack we work with is on our technology and methodology page, and each app has its own page in our apps and games.

How We Engineer Flutter Apps

The practices behind the apps on this page. Each one can be checked in an app that is live in the store.

Architecture

Widgets, state and data access sit in separate layers, so screens stay thin and logic can be tested without a device. When Flutter alone is not enough, native code sits behind a typed platform channel: AirMic's audio engine is C++, called through Pigeon.

State management

We choose per app instead of forcing one pattern everywhere. Provider covers most of our apps, Riverpod runs larger ones such as AirMic and Florea, and BLoC drives event-heavy apps such as Standby Clock.

Testing

Each of the 34 apps listed on this page has automated tests in its repository: 2,001 Dart test files between them, including 103 for Factory Legacy, 94 for LetsLearn and 39 for RadioSEM. Fourteen of the apps add on-device flows with integration_test, and Document Reader tests its BLoC logic with bloc_test and mocktail.

Data and offline use

Local data is stored with Drift, sqflite or Hive depending on its shape, and Standby Clock generates its models with freezed and json_serializable. Back ends are our own ASP.NET Core APIs or self-hosted Appwrite.

Release and monitoring

All 34 apps configure flutter_lints static analysis. Factory Legacy and Ant Empire also run flutter analyze and flutter test in GitHub Actions on pull requests and on pushes to their main branches, next to the tests of their .NET back ends. Sentry crash reporting is built into 12 of the apps and PostHog product analytics into 20, and Google Play releases go out as staged rollouts, so a problem reaches a few users before it can reach all of them.

Accessibility

33 of the 34 apps name their controls for screen readers with Flutter's Semantics widget or semantic labels, in 399 source files between them; LetsLearn alone has 47. LetsLearn also runs Flutter's accessibility guideline checks for labelled tap targets and text contrast in its widget tests, renders its screens at 1.5x and 2x text size to catch overflow, and switches its interface to right-to-left for Arabic.

Figures counted in November 2026 from each app's default branch.

Frequently Asked Questions

Common questions about building and publishing a Flutter app.

One codebase serves Android and iOS, so features reach both platforms at once and maintenance is done once. Where a feature needs native code, such as a custom keyboard or a background service, we write that part natively and keep the rest in Flutter.

Yes. All our own Flutter apps are published on Google Play, and several are also on the App Store from the same codebase. We set up the builds, signing and store listings for both platforms.

Yes. We prepare the listing, the screenshots and the data-safety and privacy forms, run the build through the store's testing tracks and release it in stages. The app is published under your own developer account, so it stays yours.

Every release reports crashes and errors to Sentry with the stack trace, app version and device. We work through new issues and ship fixes in the next update.

Yes, where the use case allows it. Data is kept on the device in SQLite, Drift or Hive and synchronised with the back end when the connection returns. Many of our own apps and games run fully offline.

Yes. We build the interface for several languages from the start, with right-to-left layouts where a language needs them. Many of our own apps ship with 11 interface languages, and LetsLearn's covers 12, including right-to-left Arabic. Where wording must be exact, such as legal or medical text, we plan a review by a native speaker with you.

You do. The source code, the signing keys, the store accounts and the back end belong to you, and you receive the documentation to build and release the app without us.

Yes. We first review the code, its dependencies and its status in the store, then agree what to fix, upgrade or rebuild before we take over releases and maintenance.

Flutter is Google's open-source SDK for building mobile, web and desktop apps from one codebase, released under a BSD licence and supported and used by Google itself. Stable versions follow a published release schedule, and the Flutter team publishes migration guides for changes that break existing code. No one can say how long any framework will last, so we keep your app on current stable Flutter versions as part of its maintenance, and the source code stays yours.

Featured Flutter Projects

Four of our own published Flutter apps, each built around a different technical problem. All four are live in the store, so you can install them and judge the work yourself.

Factory Legacy: Idle Empire

Android · iOS

An idle tycoon game built once in Flutter and published on Google Play and the App Store. Factories keep producing while the player is away, so the game works out the offline earnings when it is opened again. Cloud saves and the leaderboards run on our own ASP.NET Core and SQL Server back end, a self-hosted Appwrite pushes the live leaderboard updates, and the game is localised into several languages.

  • Flutter
  • Dart
  • ASP.NET Core (.NET 10)
  • SQL Server
  • Appwrite (self-hosted)

More about Factory Legacy: Idle Empire Google Play App Store

PixelCut Pro

Android · iOS

A photo background remover for Android and iOS. The cut-out comes from a segmentation model that runs on our own server, and the heavy pixel work - placing new backgrounds, gradients and the watermark - runs on background isolates. We moved it there after Android vitals showed large photos blocking the interface on mid-range phones.

  • Flutter
  • Dart
  • ASP.NET Core (.NET 10)
  • ONNX Runtime
  • BiRefNet
  • SQL Server

More about PixelCut Pro Case study Google Play App Store

AirMic

Android

Turns a phone into a live wireless microphone for any Bluetooth speaker. Flutter draws the interface, while echo cancellation, noise reduction and level control run in a C++ audio engine (SpeexDSP, Oboe). The two halves talk through a typed platform channel generated with Pigeon, and the microphone keeps working with the screen locked.

  • Flutter
  • Dart
  • Riverpod
  • Kotlin
  • C++17 audio engine (SpeexDSP, Oboe)
  • Google Play Billing

More about AirMic Google Play

LetsLearn

Android · iOS

A vocabulary app with 3,000 words in each of 12 languages and 132 language pairs. Flashcards follow a spaced-repetition schedule, and progress is kept separately for every language pair. The app talks to our own ASP.NET Core API and Appwrite, and product analytics run through PostHog.

  • Flutter
  • Dart
  • ASP.NET Core (.NET 10)
  • SQL Server
  • Appwrite

More about LetsLearn Case study Google Play App Store

Where we work

Rui Codex is a Belgian company and works on-site with clients across Brussels, Antwerp, Ghent, Leuven and Liège, serves clients across the Benelux (Belgium, the Netherlands and Luxembourg), and delivers projects remotely across Europe. See all service areas.

Outside the Benelux: how we work with companies across Europe.

Ready to Build Your Flutter App?

Tell us what the app should do and who will use it. We will come back with a plan for the first version, the back end and the store release.

Free consultation. No commitment. You keep the code, the signing keys and the store accounts.