BYV4 / CASEBOOK
Versions

Portfolio versions

V1 · Flutter portfolioFocused landing V2 · Flutter interactiveGames, maps, labs V3 · Next.js + Three.jsThree authored themes
V4 · Release DossierCurrent casebook

3D themes

Release BenchWarm product workshop Field ManualEditorial service document Store Review RoomInspectable evidence rail

Release dossierMY / 04

Boon Yong Yang

I build the parts that make a Flutter app shippable—then stay for store review, production feedback, and the next release.

Open the case files ↘ Start a conversation

Move across the evidence

Involve Asia app overview with affiliate offers and deeplink performance
Exhibit 01 · offer discovery
Cashiu shopping screen with cashback merchants and purchase-link entry
Exhibit 02 · cashback path
SHIPPEDiOS + Android
02 shipped products 02 mobile stores 04+ years with Flutter
Next / shipped work

00 / Operating position

The release is part of the product.

Architecture matters when the deadline moves. Native integrations matter when a user leaves Flutter. Instrumentation matters after the build reaches people. I keep those edges close enough that product decisions can still change without turning the codebase into archaeology.

01 / Shipped product dossiers

Two products.
One release habit.

Read the constraint, the engineering decision, then inspect what shipped.

Affiliate tools · iOS + Android

Involve Asia
Mobile App

The initial mobile release put offer discovery, deeplinks, reporting, analytics, and withdrawals into a product publishers could carry.

Constraint
A compressed first-release timeline across several core publisher workflows.
Decision
Establish Flutter and BLoC foundations so product flows could evolve without becoming one feature boundary.
Result
The product shipped on both mobile stores for working publishers.
App Store ↗ Google Play ↗
Involve Asia app overview with recommended offers and deeplink performance
01A / overview + deeplinks
Involve Asia discovery screen with featured brands and affiliate offers
01B / brand discovery

Cashback shopping · iOS + Android

Cashiu:
Everyday cashback

First launched as Cha Ching, the product connected merchant discovery to an affiliate handoff while keeping cashback progress understandable.

Constraint
A purchase had to leave the app for a marketplace without losing the user’s sense of status.
Decision
Connect Shopee Malaysia affiliate APIs with shopping, tracking, profile, and transaction work along one purchase path.
Result
Both stores shipped; existing accounts, wallets, and history moved into the Cashiu name.
App Store ↗ Google Play ↗
Cashiu shopping screen with cashback merchants and purchase-link entry
02A / merchant discovery
Cashiu referral screen explaining invite rewards and code sharing
02B / referral rewards

02 / Release signal

Code is only one
part of shipping.

  1. 01

    Map the product constraint

    Start with the purchase, attribution, reporting, or withdrawal path.

  2. 02

    Protect change

    Use BLoC, repositories, and native boundaries where decisions will move.

  3. 03

    Keep release close

    Make signing, automation, store delivery, and rollback visible before launch.

  4. 04

    Return the signal

    Turn crash reports, profiling, and support feedback into the next decision.

03 / Working code

Proof you can clone.

SRC—01 Flutter BLoC Starter KitArchitecture reference SRC—02 FPV Overlay ToolboxDesktop video utility SRC—03 PocketFiFinance product concept

Available for focused mobile product work

Ship the next
one with me.

boonyongyang@gmail.com
GitHub LinkedIn Kuala Lumpur / MY