Brownfield work isn’t the runner-up prize. What learning Flutter in existing codebases taught me, and why it beats starting from a blank slate.
I care about the code because I care about the people working in it
I'm a senior frontend and mobile developer with a decade of experience building things that work - and occasionally fixing things that don't.
Markdown supported · ⌘↵ to post
Rishita Sharma
The jump from URLs and browser history to a navigation stack and app lifecycles is exactly what tripped me up coming from web too. I've found the platform specific bugs only really click once you've shipped something and watched it break on a real device. Was there one Android or iOS quirk that took you longest to figure out?