Yunus Seyyar
Flutter · iOS · NestJS · Next.jsMinik Boyacı
All work

01Case studySystem view

Kids product · Mobile and content platform

Minik Boyacı

In development

An iOS-first kids product for ages 3–8 that requires no account and receives new colouring content through a controlled publishing flow.

My role
Product architecture, Flutter app, content API and admin panel
Platform
Flutter · iOS · NestJS · Next.js
Year
2026
Explore the case study

01Starting point

Case study · 2026

Kids product · Mobile and content platform

A product that begins by clarifying the need.

01AProblem

A kids colouring app needed to work in very few steps, collect no child identity and grow its content catalogue without requiring an app update.

01BSolution

The accountless Flutter experience uses an online manifest with embedded fallback content. A NestJS API and Next.js panel manage asset validation, bilingual metadata, human review and release state separately from the mobile client.

02Product and foundation

Product capabilities: 06 · Architecture decisions: 05

Flutter · iOS · NestJS · Next.js

The product and technical decisions behind the experience.

Role
Product architecture, Flutter app, content API and admin panel
Status
In development
Platform
Flutter · iOS · NestJS · Next.js

Experience scope

Product capabilities

  1. 01Touch-first landscape colouring experience
  2. 02Short-lived, in-session content cache
  3. 03Technical validation for downloaded line-art files
  4. 04Bilingual category and content metadata
  5. 05Source, rights and human-review records
  6. 06Privacy-first boundary for anonymous product analytics

How it was built

Architecture decisions

  1. 01Flutter client with no account or child profile
  2. 02Online manifest with an embedded offline fallback
  3. 03NestJS content API and PostgreSQL record layer
  4. 04Next.js content quality and publishing panel
  5. 05Parental gate for external links and purchase areas

03A closer look

01 Visual

Minik Boyacı

The product in view.

Visual 01How it was built

From approved content to play session

N/04 · R/03

  1. N01Human reviewSource · Rights · Quality
  2. N02Content panelMetadata · Release
  3. N03Content APIValidation · Manifest
  4. N04Colouring appAccountless · iOS

System connections

  1. R01Human reviewContent panel
  2. R02Content panelContent API
  3. R03Content APIColouring app
How it was builtBrand-neutral flow diagram connecting a mobile colouring app, content API, review panel and release manifest

04Outcome

In development

In development

Where is the product today?

The product is in development. Illustrations without completed rights and human review are excluded from the portfolio, so this case only presents the product flow and safe content architecture.