How I can help

Senior Android and frontend help, hands-on or as a lead.

I've spent 7+ years shipping production Android apps in fintech, health tech, and iLottery, about two of them as an Android tech lead, and I now work in Vue, TypeScript, and Phaser too. Here are three concrete ways I can help. If your situation fits none of them, tell me about it anyway.

Contract or lead

Android engineering and tech leadership

A senior Android engineer who can join an existing team and deliver features, or lead the team and improve how it builds.

Useful when

  • Teams that need senior or lead Android capacity on a contract basis
  • Codebases moving to Jetpack Compose, Coroutines and Flow, or a cleaner architecture
  • Teams whose test coverage, review practice, or release confidence has slipped

Typical outputs

  • Features in Kotlin and Jetpack Compose
  • Architecture refactors, modularisation, and test strategy
  • Code review, mentoring, and pair programming

Format: Part-time or full-time contract, embedded with your team

Build

Mobile and web product builds

A focused first version of a mobile or web product, built by one senior engineer from the critical path to the release.

Useful when

  • Founders who need a real Android app or web MVP rather than a throwaway prototype
  • Teams that need a contained feature or companion app built and handed over cleanly

Typical outputs

  • Native Android in Kotlin and Compose, or a web frontend in Vue or React with TypeScript
  • Store or web release preparation
  • Documentation and a maintainable handoff

Format: Fixed-scope or milestone-based contract

Review

Android architecture and codebase review

An outside senior view of an Android codebase, with a short, prioritised plan your team can act on.

Useful when

  • Teams preparing to scale, hand over, or modernise an Android app
  • Engineering leads who want an independent read on architecture, testability, and build health
  • Teams adopting AI coding tools who want guardrails that fit their codebase

Typical outputs

  • Written review with prioritised findings
  • Refactoring and testing plan
  • Walkthrough call with the team

Format: Fixed-scope, fixed-price review

Also: AI and MCP integrations

Give AI the right context.
Keep the boundary visible.

I build and operationalize MCP integrations that connect AI assistants to project knowledge, real workflows, and human-approved actions. The protocol is only the interface; the product still needs clear state, permissions, review, and failure behavior.

Project brain + MCP

Context that survives the conversation.

A project brain keeps the mission, evidence, constraints, decisions, progress, and outcomes attached to the product. MCP exposes only the context and actions a workflow actually needs.

  • Project-scoped knowledge and source ingestion
  • Typed MCP tools, context contracts, and integration boundaries
  • Proposal, review, confirmation, and audit flows
  • Packaging, health checks, tests, and operational handoff
Read the field note
Continuum

Local product integration

A development-only MCP boundary can validate and export declarative product models or stage a change for review. The running application—not the protocol client—owns approval.

Postiz Chat Bridge

Remote operations workflow

A private Marketing Brain grounds campaign and profile work in project evidence, while external publishing actions remain separated behind preview, immutable approval, and explicit confirmation.

Where this stands: I've built these integrations for my own products. If you need something similar, it fits best as part of a build or review engagement.

How I use AI

Models in the loop.
Judgment at the center.

I use AI to shorten the path from an ambiguous question to a reviewed, useful output. The leverage comes from fitting models into a clear product workflow—not asking them to replace context, verification, or responsibility.

01 · Explore

Turn raw context into options.

Synthesize research, test alternative directions, and create rapid prototypes before committing to the expensive path.

02 · Build

Accelerate the critical path.

Use engineering assistance for implementation, failure-case exploration, QA, tests, and documentation—then verify it against the real product.

03 · Operate

Make repeatable work repeatable.

Connect content variation, launch assets, and production steps into workflows with explicit review and approval points.

Next step

Tell me what you need.

A few sentences about the role, product, or codebase are enough. I reply to every relevant message by email.

Work with me