Skip to content
Mobile Byte Sensei

Core services, and any product your requirement calls for.

Mobile, games, web, desktop, applied AI, and the design and planning that precede them, delivered by dedicated engineering, design, QA and operations teams. Requirements outside the core services are scoped on the same terms.

Request a proposal Browse the core services

Written response within one week. No preliminary sales call.

Core services.

The services requested most often, each with a defined scope, a stated engagement shape and a page setting out its limits. They are examples of what we deliver, not the limit of it.

  • Mobile apps

    Android and iOS apps, native or on a shared codebase where the product and the team justify one.

    • Shared-code apps
    • Platform surfaces that stay native
    • Offline-first storage
    Duration
    4–8 months
    Team
    2–4 people
    Starts
    Discovery sprint, then monthly

  • Games

    Casual and children’s games, from playable prototype through store submission and live operations.

    • Casual and children’s games
    • Prototype to release
    • Remote configuration and live events
    Duration
    6–12 months
    Team
    3–6 people
    Starts
    Prototype review

  • Web platforms

    Dashboards, product sites and the data layers behind them, built to perform on a mid-range phone.

    • Product sites with programmatic SEO
    • Multi-brand site shells
    • Next.js marketing and content sites
    Duration
    3–9 months
    Team
    2–5 people
    Starts
    Discovery sprint, then monthly

  • Desktop software

    Windows, macOS and Linux applications for workflows that do not belong in a browser.

    • Compose Multiplatform desktop apps
    • Native installers
    • Signing and certificates
    Duration
    4–9 months
    Team
    2–4 people
    Starts
    Discovery sprint

  • Applied AI

    On-device speech and language models, and the evaluation work that decides whether a feature ships.

    • On-device speech recognition
    • On-device language models
    • Models sized to the device
    Duration
    2–6 months
    Team
    2–3 people
    Starts
    Feasibility sprint

  • Design & planning

    Product definition, scope and interface design, delivered as a fixed-fee engagement.

    • Idea to plan
    • App-flow mapping
    • Reusable flow patterns
    Duration
    2–6 weeks
    Team
    1–2 people
    Starts
    Fixed fee, credited against a build

  • Something else?

    Describe the requirement. Any other application or product is scoped against it.

    Delivered on the same engagement terms as the core services.

    Duration and team are set after scoping.

Durations and team sizes are indicative, not a quotation. Terms are confirmed in writing after scoping.

Also delivered.

Specialist, operating and advisory lines, on their own or inside a core engagement.

Something else? Describe the requirement.

  • Developer tooling and SDKs

    Libraries, Gradle and IDE plugins, published to Maven Central.

  • Payments and monetisation

    Subscriptions, purchases and ads across the stores, Stripe and Razorpay.

  • Analytics and remote configuration

    Event instrumentation so post-launch decisions rest on data.

  • Kotlin Multiplatform migration

    Staged moves from an Android codebase, starting with an audit.

  • CI/CD and release automation

    Reusable pipelines for builds, versioning and release notes.

  • Release and store operations

    Listings, signing, testing tracks and staged rollouts on every store.

  • Cloud and delivery infrastructure

    Environments, secrets and the backend services a product ships on.

  • Quality engineering

    Automated suites, device-matrix and accessibility testing in CI.

  • Operations and reliability

    Monitoring, crash triage and on-call for software in production.

  • Embedded engineering teams

    Named engineers working inside your process and backlog.

  • Technical advisory and audit

    Codebase, architecture and due-diligence reviews with written findings.

  • Technical documentation

    API references and documentation sites published with each release.

  • Product websites and legal pages

    Product sites with privacy, terms, refund and support pages.

Engineering we publish.

Open-source libraries, build tooling and CI workflows we maintain in public and use in our own products. Status is shown only where confirmed.

Technologies in our own work.

Listed only where our products and tooling use them. The stack for a client is chosen per engagement, and where a client already runs one, the work proceeds within it.

  • Mobile

    • Kotlin
    • Jetpack Compose
    • Kotlin Multiplatform
    • Compose Multiplatform
    • Swift

  • Web

    • TypeScript
    • React
    • Next.js
    • Astro
    • Tailwind CSS

  • Backend and data

    • Supabase
    • PostgreSQL
    • Firebase
    • Ktor
    • Room
    • Python

  • Desktop and games

    • Compose Multiplatform
    • Kotlin
    • Fastlane

  • Applied AI

    • Whisper
    • whisper.cpp
    • llama.cpp
    • sherpa-onnx
    • LiteRT

  • Infrastructure

    • GitHub Actions
    • Docker
    • Cloudflare Pages
    • Netlify
    • Vercel

How engagements run.

Three stages, each producing work you own and can take elsewhere. Terms, reporting and what each stage needs from you are set out on the process page.

The process in full

  1. Discovery sprint

    2–3 weeks Fixed fee

    For a defined problem where the shape of the build is not yet known.

  2. Build engagement

    3–9 months Monthly retainer

    A dedicated team delivering working software in two-week increments.

  3. Hold and improve

    Rolling Monthly retainer

    After launch, for products that must remain operational and continue to improve.

Questions before a brief.

Each service page answers the questions specific to it.

All questions

Can you build something outside the listed services?

Yes. The services on this site are the ones requested most often, not a complete list. Any application or product can be scoped against its requirement.

That work is delivered by dedicated engineering, design, QA and operations teams, on the same engagement terms as the core services.

How do we start?

With a scoping engagement: two to three weeks at a fixed fee. It concludes with a written plan, an estimate as a range, a risk register and a clickable prototype of the flow that carries the product.

The fee is credited in full against a build engagement that starts within 90 days. That credit is written into the contract.

How big is the team on a project?

Usually two to five people, agreed before the engagement starts. The agreed size does not change without your agreement.

The same people stay on the work for its full length. Rotating staff to balance utilisation protects a supplier’s margin at the cost of the client’s context.

Can you take over someone else’s codebase?

Yes, regularly. It starts with a paid two-week audit before either side commits, because inheriting a codebase without one leads to unreliable estimates and avoidable cost for the client.

Sometimes the audit concludes that a rewrite is cheaper than a rescue. You receive the reasoning as well as the recommendation.

Is there work you turn down?

Games built around aggressive monetisation of vulnerable players. Models placed in decisions that materially affect someone’s life without a human review path.

This position costs us work, and it is maintained regardless.

Request a proposal.

Submit the requirement, for a core service or anything else, and receive a written assessment with an indicative estimate and the risks identified at this stage.

Request a proposal Something else? Describe the requirement.

Or write to hello@mobilebytesensei.com

Response
In writing, within one week
Contents
Assessment, indicative estimate and identified risks
Sales call
Not required before the written response
Discovery fee
Credited against a build engagement starting within 90 days