floguo's artifacts
floguo.com · 1,842 words · saved by 1 readers
personal website of flora guo
The web feels direct. You click Save, the button changes, and your work is there when you return tomorrow. Underneath that moment is a conversation between computers. The browser turns code into an interface. A server applies the product's rules. A database keeps what should survive after the tab closes. The internet carries messages between them. You do not need to become an engineer to design for this system. You do need a rough map of it. The map helps explain why a screen loads in pieces, why a form can fail after submission, and why a seemingly small feature can require a change to…
saved by
related reading
- Resources - ui.landui.land
- Frank Chimero · What Screens Wantfrankchimero.com
- Design Engineeringfloguo.com
- The Descent — What Happened to the Frontend While You Weren't Watchingdavidpoblador.com
- 7 Principles of Rich Web Applicationsrauchg.com
- Building data-centric apps with a reactive relational databaseriffle.systems
- Web Browser Engineeringbrowser.engineering
- Paco Courseypaco.me
- Frank Chimero · The Web’s Grainfrankchimero.com
- Learning From Terminals to Design the Future of User Interfaces — brandur.orgbrandur.org
- Web Interface Guidelinesvercel.com
- Design with materials, not features | thesephist.comthesephist.com