Every state, not just the happy path
Loading, empty and error screens get the same attention as the success screen.
Frontend developer · open to opportunities
I work mostly in React, and I care about the parts people only notice when they're missing: the loading spinner, the helpful error, the empty state that tells you what to do next.
@developer-prachi
About me
I'm a frontend developer who started with hand-built HTML & CSS layouts and grew into React apps that talk to real APIs. I like keeping things simple: the smallest amount of state that works, components that do one job, and code that explains itself.
Loading, empty and error screens get the same attention as the success screen.
If a value can be calculated from existing state, it isn't stored twice.
Each README says what's a demo, what's real, and what I'd do next.
Selected work
Recent React apps, each deployed and open source. Click through and try them.
The archive
Contact
Have a role, a project, or just want to talk frontend? My inbox is open.
github.com/developer-prachi ↗