コンテンツへスキップ

FieldsSoftware DevelopmentMobile Developer

Mobile Developer

Build the apps people carry in their pockets.

Career

Structure
8 modules, each ending in a milestone
Proof
Verified against real tasks from module 2
Ends in
A defended capstone and a high-assurance credential

Get early access

The journey

  1. Practised under observation

    1. The mobile platform and a first appHow a phone runs software, and the platform's own language taught from zero.Practised under observation
      MilestoneSpeaks the platform's language

      You write in the platform's own language, and you can account for the bargain your app strikes with the device that runs it.

  2. From here, milestones are verified rather than practised.

    Verified against a real task

    1. App components and the lifecycleYour app is a guest of the operating system, and every screen has to survive what the system does to it.Verified against a real task
      MilestoneSurvives the operating system

      The system can suspend your app and end it without warning, and the person who comes back finds exactly what they left.

    2. Interfaces: declarative depth, classic literacyState-driven interfaces at depth, the installed base read fluently, and the platform's own design language taken seriously.Verified against a real task
      MilestoneNative to the platform's eye

      An interface built from state rather than from instructions, at home in the platform's design language, and still smooth on a list with no end to it.

    3. Architecture, state and concurrencyArchitecture chosen for this app rather than for fashion, state flowing one way, and concurrency that never blocks the person using it.Verified against a real task
      MilestoneArchitected and concurrent, honestly

      Work happens off the interface thread so nothing stalls under a person's finger, and the structure you chose can be defended against the simpler one you did not.

    4. Data, networking and offline-firstThe unreliable network as the default assumption, with local truth persisted properly and sync that holds.Verified against a real task
      MilestoneTrustworthy in airplane mode

      In a tunnel the app is still worth opening, and what it syncs when the signal returns arrives once and correctly.

    5. Quality: testing, verified accessibility and security on the deviceTests that catch, profiling that finds the real leak, accessibility proven with the platform's own tools, and a security posture for software in strangers' pockets.Verified against a real task
      MilestoneProven on the device

      Someone using a screen reader can run the whole app, nothing secret travels inside what you ship, and the leak or the stall is found with tools rather than guessed at.

    6. Device capabilities, platform services and the cross-platform decisionDevice capabilities behind their permission gates, background work inside the system's rules, and the native or cross-platform decision made like an engineer.Verified against a real task
      MilestoneCapable, restrained, decided

      Every capability earns the permission it asks for and behaves when refused, and building native or not is an argument you make from this product rather than from taste.

    7. Shipping and the Mobile Developer in the organizationThe release craft this seat is defined by: signed builds, staged rollouts, and software you cannot hotfix.Verified against a real task
      MilestoneShipped, watched, professional

      A release you cannot take back goes out in stages, watched, and the decision to stop it was made before it was needed.

    1. Capstone

      An app strangers install

      A complete production app for a real domain, built under observation on your chosen platform, from a first screen through to a signed release in a beta channel with monitoring wired and its own known limitations written down.

      Defence

      You walk an instructor through your own app: what the operating system may do to it and how it survives, who cannot use it and why that is acceptable or is not, where a secret could leak and why it cannot, and what you would do first when it crashes on a device you have never owned. The credential is not awarded if you cannot account for your own work.

    2. Credential

      High-assurance credential

      Evidence that you can ship apps that survive strangers' devices, real networks, and store review. It does not claim seniority, and it does not oblige any employer to accept it.

      See how proof works

Related capability paths

What is not live yet

The desktop app, consent-based observation, scoring, and credentials are in development. Nothing here implies they are live yet.

Get early access