professor curious (fka zuai)

this was my first internship. i had written flutter on my own, but i hadn't worked inside a real team or a real codebase. day one meant figuring out branches, prs, and code review, the practical side of shipping with other people.

the bar was higher than my college side projects. the app was already live and being used.

i built parts of the onboarding and dashboard screens in flutter. tiny surfaces but every new user hit them. that meant honoring loading, empty, and error, not only the sunny path.

the app needed to handle 500k+ users across patchy networks, so i used riverpod for state and dio with retries and timeouts for the api layer.

i added dark mode across the screens i owned and nudged general ui polish along the way (spacing, type scale, hit targets). boring on paper but it keeps the product from feeling janky.

this was where i first learned that detail work compounds. shipping a ticket isn't always the same thing as finishing it.