Field notes of a mobile product engineer

I buildmobile productsfrom messy ideas.

Mobile Product Engineer combining Flutter engineering, product thinking, ownership, and visual storytelling.

Production applications · Android and iOS releases · 10,000+ cumulative downloads

Explore the experiments About the person behind them Résumé

The engineer

SimpliEd Teacher app dashboard — SimpliEd — live on Android & iOS

what if the alarm refuses to stop until you actually sit up?

Still questioning · drag me

Built in Flutter

// outbox.dart — offline write path
queue.add(write);        // offline
await replayInOrder();   // reconnect

Android + iOS3.2s → 1.76s

The engineer

what if the alarm refuses to stop until you actually sit up?

Still questioning · drag me

Android + iOS3.2s → 1.76sBuilt in Flutter

10,000+
cumulative downloads
↳ team/product outcome — I build & ship the mobile layer
3.2s → 1.76s
initial load
↳ profiled first, then restructured
Android / iOS
production releases
↳ TestFlight · Play Internal Testing
build → test → release
end-to-end contribution
↳ code to store, both platforms

01 / Selected work

Selected product experiments

Each project is a documented investigation — from the first observation to what shipped, what was rejected, and what it taught me.

Experiment 01 / Production systemProduction · live on Android & iOS

Building and improving a learning platform with 10,000+ cumulative downloads

Owning mobile features and releases across a production education platform — two live Student and Parent apps and an offline-first Teacher app with an encrypted local database and durable sync. Production work under confidentiality.

Observation

Teachers lose work when classroom connectivity fails.

Question

Can the app stay reliable without depending on a live API at all times?

Response

An encrypted local database as the source of truth, with durable queued synchronisation.

Read the investigation

Flutter
Dart
Riverpod 3.x
Drift (SQLite)
Firebase
REST

Local DB
Outbox
Sync
REST API

SimpliEd Student app home with modules for circulars, news, events, attendance, timetable and gradebook

SimpliEd Teacher app dashboard showing today's classes, quick actions, pending grading and the day's schedule

SimpliEd attendance flow scanning a student QR code and marking the student present

3.2s → 1.76s

Initial load, profiled first

TestFlightPlay Internal

Experiment 02 / Habit designIn active development · not yet published

Designing an easier way to understand and maintain everyday spending

An independent budgeting product designed to reduce the friction of recording expenses, understanding spending patterns, and maintaining financial habits — with an AI advisor as a supporting feature, not the point.

Observation

Recording an expense is easy. Keeping at it is the part everyone quits.

Question

How small can a single entry get before the habit stops feeling like admin?

Response

Local-first capture with category and monthly totals that update instantly — sync can wait.

Read the investigation

Flutter
Firebase
Gemini AI
Clean Architecture
GitHub Actions

lower entry friction → the habit survives

Current hypothesis · needs user testing

Entry in seconds
Category budgets
Monthly totals

Experiment 03 / Behavioural prototypeConcept / prototype · needs validation

Designing an alarm that requires a real sign of waking up

A mobile product experiment exploring whether physical posture detection can reduce unconscious snoozing while remaining safe and accessible — prototyped in Flutter and documented as a build-in-public series.

Observation

People silence alarms without ever actually waking up.

Question

What counts as real proof of being awake — and is it safe to demand it?

Response

A posture signal (sitting up), with an accessible fallback. Still a hypothesis under test.

Read the investigation

Flutter
Device sensors

Prototype — not validated

Dismissal requires a real sign of waking

false positives: phone on table

accessible fallback required

sensors stay on-device

Open the full index

02 / Process

How I think

Six stages I actually move through — each one tied to a real example from shipped work. Select a stage to see it.

What is frustrating, confusing, slow, repetitive, or unnecessarily difficult?

From Stupid Alarm

Watching people silence an alarm without actually waking up became the seed for Stupid Alarm.

It rarely runs in a straight line — what production teaches loops straight back into what I notice next.

Ownership map

What I touch in a product

Honest boundaries, drawn as a map: what I own today, what I contribute to alongside the team, and what I'm deliberately growing toward.

I currently own line style: I currently own
I regularly contribute to line style: I regularly contribute to
I'm growing toward line style: I'm growing toward

03 / Creative

Observations that became stories

The same habit that drives the product work — noticing something small and following it — pointed at people instead of software. Video opens on YouTube; nothing autoplays here.

Observation 01

Why do people wait for a call to end before sending a text?

Why I Wait for the Call to End Before I Text

A tiny everyday habit, followed until it becomes an observation about attention.

Medium: Personal video essay
Demonstrates: Human observation and narrative structure

Watch

Observation 02

Why do builders ship for everyone except themselves?

I ship apps for everyone except myself.

A developer's confession about building products for everyone else while putting your own on hold.

Medium: Developer reflection
Demonstrates: Product reflection and technical communication

Watch

Observation 03

Can an alarm demand proof that you're actually awake?

Stupid Alarm — building in public

The build story behind the behavioural alarm experiment: the hypothesis, the sensor problem, and what breaks.

Medium: Build-in-public dev series
Demonstrates: Building in public and product ideation

In production

The person behind the experiments

Karachi → remote · Flutter by trade, storytelling by habit

04 / About

Engineering gave structure to my creativity.

I spent years experimenting with video, design, photography, and storytelling before moving deeply into mobile development. Those interests were never separate — they taught me how people notice, understand, and respond to experiences. Today, I use that perspective to build mobile products that are reliable, thoughtful, and easier to communicate.

I want to understand why something should exist — not only how it should be built.

Read the full story

05 / Contact

Building a mobile product or team?

I'm open to remote mobile roles, startup teams, and selected product-development opportunities where thoughtful execution and ownership matter.

syeduzaifamin@gmail.com

Based in Karachi, open to remote opportunities and relocation to Islamabad or Rawalpindi.

I buildmobile productsfrom messy ideas.

Selected product experiments

Building and improving a learning platform with 10,000+ cumulative downloads

Designing an easier way to understand and maintain everyday spending

Designing an alarm that requires a real sign of waking up

How I think

What I touch in a product

I currently own

I regularly contribute to

I'm growing toward

Observations that became stories

Engineering gave structure to my creativity.

Building a mobile product or team?