Sydney's public transport is complicated enough. KRAIL brings real-time trains, buses, ferries, metro, and light rail into one clean, accessible app. Kotlin Multiplatform, open source, live on both stores.
A snapshot of what I'm building, shipping, and reading.
Leading platform work for Android and iOS at Commonwealth Bank: shared architecture, engineering standards, and the internal agents and MCP servers the mobile teams build with.
ASTRAMAN turns a design handoff into a Kotlin Multiplatform app: agents plan, write, and review each build. It sits on a library of Claude Code skills I use on every app.
Open-source iOS + Android in Kotlin Multiplatform, with a Ktor backend. Live on both stores. Presented at Google I/O Extended Brisbane 2025.
Engineering posts on Kotlin, Compose, security, and accessibility.
Consumer apps and open-source libraries in Kotlin Multiplatform. Started from real frustrations: transit apps that fail commuters who need accessibility, games that deserve better craft, tools that should just work.
Sydney public transport for iOS & Android.
Sydney public transport shouldn't be stressful. KRAIL covers trains, buses, ferries, metro, and light rail: real-time, accessible, and open source. Kotlin Multiplatform, presented at Google I/O Extended Brisbane 2025.
Small, finished apps. Each built in Kotlin Multiplatform for iOS and Android.
A daily Sudoku that respects your attention. Ink on paper aesthetic, five difficulty levels, streak tracking. No noise, no ads, no dark patterns. Just the puzzle.
A color-perception game built around Delta-E science. Identify the outlier from near-identical hues. Starts forgiving, gets quietly brutal. Ranked by accuracy, not just speed.
Kotlin Multiplatform, like the rest, and the first one built end to end by ASTRAMAN.
Libraries and apps I maintain in the open. Everything else lives on GitHub.
Sydney public transport app for iOS & Android. Built with Kotlin Multiplatform & Compose.
The Ktor backend behind KRAIL: trip planning over the NSW transport network, Protobuf contracts, containerised deploy.
A Kotlin Multiplatform location library for Android and iOS. Sanskrit-named, one API across platforms.
A Kotlin Multiplatform permission library for Android and iOS. Runtime permissions without the per-platform boilerplate.
Zen Sudoku. Kotlin Multiplatform + Compose for iOS and Android. A daily puzzle built around stillness.
A color-matching game for curious minds. Kotlin Multiplatform + Compose, iOS and Android.
Shared API data contracts in Protocol Buffers, the typed boundary between KRAIL's app and backend.
Alongside the apps, I build the tooling that helps make them: Claude Code skills, MCP servers, hooks, and agents that handle the repetitive parts of a Kotlin Multiplatform build. Some of this is for the mobile teams at Commonwealth Bank. The rest is for my own apps, mostly on evenings and weekends.
A design handoff goes in. A Kotlin Multiplatform app comes out.
A set of Claude Code agents runs in sequence. One reads the design files and writes a phased build plan with the design tokens. One writes the Kotlin Multiplatform code phase by phase and commits as it goes. A reviewer runs a quality gate after each phase and records what went wrong. A fourth reads finished builds and proposes edits to the other agents' instructions, so the next build starts from what the last one taught.
Each build runs in its own workspace and session, so more than one app can be in progress. The foundation is not regenerated per app: it comes from a verified template, so the base is the same every time and the agents only write what differs.
The pieces that make this repeatable rather than a lucky prompt.
The work that repeats on every Kotlin Multiplatform app is written down once as a skill: modularisation, Koin, Navigation 3, SQLDelight, Ktor, Compose resources, typography, colour tokens, app icons, in-app purchases, CI/CD, font-scale accessibility, release checks. Writing it down once is cheaper and more predictable than explaining the same setup to a model each time.
New apps start from a KMP template that already builds: multi-module structure, convention plugins, DI, static analysis, testing, and an empty component catalogue. Creating a project from it is a copy and a rename, so nothing about the foundation is left to chance.
Subagents with narrow tools, hooks for the rules that must not be skipped, MCP servers when a model needs real data rather than a guess, and git worktrees so parallel agents do not collide. Most of the work is deciding what context each agent gets, and what it is not allowed to do.
KRAIL needs video to reach people, so I build the videos with code.
A video is a config object rather than a timeline. Scenes, copy, colour, spacing, and motion are fields in a schema, and a React and Remotion engine renders them to a vertical video. Nothing is hand-animated per video, so adding a capability means adding a field to the schema, and the look stays consistent across everything that goes out.
Around the engine there is a small dashboard for the parts that are not rendering: the script for each video, per-platform captions for Instagram, TikTok, YouTube Shorts, Facebook, Reddit, and LinkedIn, a queue of what to build next, and the posting calendar. The videos are built from the Claude CLI with a skill I wrote for it.
Leading AI strategy and readiness for mobile engineering, on Android and iOS.
Internal MCP servers, including one for the design system, so generated UI is built from the components, tokens, and rules the design team actually ships rather than an approximation of them.
Agents and skills that turn designs into Compose code, generate UI, handle repetitive dev work, and write end-to-end tests.
A Jetpack Compose linting system that checks architecture and design-system standards across teams, so reviews spend less time on style. Alongside it, training engineers across the org on AI-assisted development.
The rest of the workshop around my own apps. One is open source, the others stay private.
A Ktor service for trip planning over the NSW transport network, with Protobuf contracts shared with the app and a containerised deploy.
Design tokens in the W3C format, compiled once into Kotlin and Swift, with catalogue apps in Jetpack Compose and SwiftUI so both platforms read from the same source of truth.
Pulls KRAIL's own analytics exports into local storage and a small dashboard, because the hosted retention window is short and the export tools are slow to work with.
Training engineers on AI-assisted development, and mentoring on what holds up in a large codebase.
Training and mentoring engineers at work
Staff Software Engineer at Commonwealth Bank, building the CommBiz business-banking app from the ground up on Android and iOS, and leading AI strategy and tooling for mobile engineering. Before this: Cash App, Afterpay, Telstra, Zip, and Qualcomm. Outside work I build and maintain KRAIL, Sumi, and Huezoo, along with the agent tooling that helps ship them.
Since 2015: Android, then iOS, now Kotlin Multiplatform everywhere.
Banks, fintechs, telcos, OEMs and healthcare startups. Two continents.
KRAIL, Sumi, and Huezoo. Open source and actively maintained.
Sharing what I learn, and helping the engineers and teams around me grow.
Google I/O ExtendedBrisbaneJun 2025
Mentoring & talks for engineering teams
Engineering posts on Kotlin, Compose, security, accessibility, and the parts of the job nobody schedules.
The one I'd hand a new engineer joining a Compose codebase.
What I wish I'd known three migrations ago: modifier hygiene, slot APIs that age well, and designing for the engineers who'll inherit your code two years from now.
Newest first.
A few photos from places I've wandered through.
