Cross-Platform Engineering
- Kotlin Multiplatform shared domain logic
- Compose Multiplatform UI structure
- Platform abstraction with practical boundaries
- Deterministic state and local data models
I’m Xinggen Guo, an independent software engineer with 10+ years of Android product experience. I work across Kotlin Multiplatform, backend APIs, deployment, and product structure — turning unclear ideas into usable systems.
I build across the full product surface instead of staying inside one layer. My background spans Kotlin Multiplatform apps, Android engineering, Node.js backends, deployment, product structure, and early-stage product delivery.
Over the years, I have worked on consumer apps, audio/video features, internal tools, account management systems, mini-program products, and independent software projects. I care about how a product is structured from the inside: how data flows, how features grow, how the backend supports the client, and how the whole system can evolve without becoming fragile or unnecessarily complex.
This portfolio is not designed as a landing page for one product. It is a personal site that shows how I think, build, and connect different layers of software work.
My work is less about presenting a polished product shell and more about showing the process behind product construction: turning unclear requirements into structure, building usable systems, solving technical problems, and keeping the product flexible enough for the next stage.
Turn unclear requirements into modules, flows, data models, role boundaries, and delivery stages.
Build Android and KMP apps with shared domain logic, practical UI structure, and release-ready implementation.
Design APIs, database structure, authentication, data processing, and service logic that actually support the client.
Ship through VPS, Docker, Nginx, HTTPS, Cloudflare, and the release workflows needed to keep delivery stable.
These are the clearest examples of how I work: building products, shipping client systems, structuring tooling, and researching difficult technical behavior when the implementation details matter.
A full-stack WeChat Mini Program for project collaboration, covering role-based access, stage tracking, document workflows, time logging, and audit history in one lightweight system.
Technical research into selected regional payment apps and utility apps, focused on Android internals, interface behavior, native C/C++ logic, encrypted data flows, and structured technical reporting.
A Kotlin Multiplatform local account vault app for Android, iOS, and Desktop, built to organize multiple identities, linked accounts, and sensitive local data with lightweight editing and field-level encryption.
A cross-platform UNO-style card game built with Kotlin Multiplatform and Compose Multiplatform. The current product is a local single-player experience against AI, with shared core gameplay logic and most UI across Android, iOS, and desktop.
A multi-surface product case covering H5 pages, admin web, backend services, and Kotlin Multiplatform mobile work, with coordination across product flows and delivery boundaries.
A calm, local-first to-do app for Android, iOS, and Desktop, built for personal daily use with fast capture, light organization, archive-based history, and a separate recurring-task system.
A full-stack remote job platform built around search, aggregation, backend ingestion, and practical deployment on self-managed infrastructure.
A personal tracking app for recording daily behavior and building structured self-observation data with a local-first cross-platform architecture.
A focused productivity timer project built to keep the feature set minimal while the state model, domain logic, and cross-platform UI structure stay clean.
A Kotlin Multiplatform location product centered on saved places, map-based workflows, and modular persistence that can evolve across Android, iOS, and desktop.
A practical utility repo that combines desktop automation scripts, game helpers, document conversion utilities, and network-service tooling.
A narrative adventure game prototype built with Cocos Creator and TypeScript, using scene-first storytelling, light survival systems, and chapter-driven progression instead of text-heavy UI.
I work well in projects where the requirements are still moving, the system surface is larger than expected, and someone has to connect product structure, implementation detail, and final delivery.
Before working independently, I had already spent 10+ years building Android products in consumer internet environments, including audio/video features, app stability work, data collection, release workflows, and product iteration. That background shaped how I design systems today: practical first, clear in structure, and built to survive real product changes.
Solid structure before feature accumulation, so the system remains maintainable.
Core business logic should stay separate from IO, frameworks, and platform specifics.
Shared code only where it simplifies the system and carries real product value.
Predictability matters. Good systems are understandable before they are clever.
Working software and feedback beat abstract purity when building real products.
Every feature sits inside a larger operational and architectural system.
Long-distance cycling across multiple countries gave me a different kind of systems training: planning under constraints, adapting daily, and staying calm when the environment stops being predictable.
A long-distance tour is a logistical system where resource management, equipment reliability, risk control, and mental resilience are tested every day.
I carry that same resilience into software work, especially when a system needs to stay durable while requirements, priorities, and delivery pressure keep moving.
Open to remote contract work, Android and KMP architecture, cross-platform product development, backend API work, reverse engineering research, and early-stage product system design.
Email me with your product stage, current problem, expected delivery timeline, and budget range.