Senior iOS Engineer · Taiwan

I build products where intelligence is infrastructure.

10+ years shipping production iOS products. Now using AI-assisted development to build products with clear validation, user control, and recovery.

10+
years shipping
~100K
DAU · real-time
~20K
DAU · wallets
01Intent
02Structure
03Evidence
04Recovery
AI ASSISTED System
Scroll to inspect

AI, STRUCTURALLY

AI is not a feature. It is a new product contract.

The interface can feel fluid. Underneath, authority, truth, recovery, and evidence stay explicit.

01

Intent → contract

Natural language becomes an editable, bounded structure — never an opaque command.

02

AI proposes. Product owns.

Validation, rendering, persistence, and recovery remain deterministic product responsibilities.

03

Human authority

The user can inspect state, understand the next action, and stop unsafe mutations.

04

Evidence over theater

Receipts, checks, and recovery paths matter more than an agent merely appearing busy.

SELECTED COMPANY PRODUCTS

Products I contributed to in production.

Selected contributions made as part of engineering teams across self-custodial wallets, real-time betting, and connected mobility.

01 / WALLET
Crypto.com Onchain app icon

Crypto.com Onchain

Owned iOS Earn across multiple blockchain protocols. Shipped staking, rewards, position management, and Buy & Swap for a self-custodial wallet.

~20K
DAU
iOS
Ownership
Multi-chain
Protocols
Company product ↗
02 / REAL-TIME
SportyBet app icon

SportyBet

Built live odds, open bets, and betting-history synchronization. Prevented duplicated WebSocket updates across multiple betting slips and evolved legacy modules.

~100K
DAU
WebSocket
Live state
RxSwift
Migration
Company product ↗
03 / MOBILITY
KINTO Unlimited app icon

KINTO

Delivered vehicle usage tracking, vehicle status, and in-app guidance for a connected vehicle application on a focused three-month production cycle.

3 mo
Contract
Vehicle
Live state
iOS
Production
Company product ↗

HOW I BUILD

Product clarity before model cleverness.

  1. 01

    Define the truthful outcome

    Name the user problem, observable done condition, and what the product must never claim.

  2. 02

    Separate intelligence from authority

    Let models interpret and propose; keep validation, persistence, and mutations behind explicit contracts.

  3. 03

    Design failure and recovery

    Treat checkpoints, stale writes, degraded modes, and receipts as product surfaces — not backend trivia.

  4. 04

    Verify the experience

    Prototype the interaction, test deterministic gates, then measure whether the system helps the user move.

BUILD THE NEXT SYSTEM

If the product needs both imagination and operational truth, let's talk.