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.
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 + MCPContext 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 →ContinuumLocal 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 BridgeRemote 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.