The saddest designer An Essay by Chia Amisola chias.blog I am tired of the premise that creation means productivity––especially in the laborious sense...Creation has become mangled with labor in a world that demands man to monetize all of their hobbies and pursuits. In return, it seems empty, almost sad, really––to be the designer spending weekends again on the screen. To tell you what I like to do in the weekends, I like to do the sad thing...The ‘good’ people tell you to detach your life from your workspace, but this summer, I think I’ve just realized how much I adore what I have the luxury of working on everyday. In the weekend, I make. I make not because it’s the only thing I have ever known, but because it’s the most certain way forward. To see the fulfillment of the workYour life adds up makingidentitywork
The web in decay is the web by design An Essay by Chia Amisola chias.blog When will there be a guide to best practices for archiving the web? Will the giants responsible for the platformization of the web make the act of digital archival any easier for us? Is it foolish for platforms like Snapchat or Instagram Stories to brand themselves as “temporary” when temporariness is impossible on our internet? Should the web exist as something organic, malleable, and destructible –– or as an eternal timekeeper? Is link rot more of a technological issue or a human one? Do humans want to know themselves forever? The Internet Is Rotting decaywww
In defense of disorder: on career, creativity, and professionalism An Essay by Chia Amisola chias.blog Professionalism is a lie, build what you love, explore everything. In today’s age of creation, anyone who attempts to tell you otherwise is lying. You’ll end up seeking what you traded for the rest of your life. Successful careers are not planned workcreativitybureaucracy
The Fidelity Curve An Article by Ryan Singer m.signalvnoise.com How do we choose which level of fidelity is appropriate for a project? I think about it like this: The purpose of making sketches and mockups before coding is to gain confidence in what we plan to do. I’m trying to remove risk from the decision to build something by somehow “previewing” it in a cheaper form. There’s a trade-off here. The higher the fidelity of the mockup, the more confidence it gives me. But the longer it takes to create that mockup, the more time I’ve wasted on an intermediate step before building the real thing. I like to look at that trade-off economically. Each method reduces risk by letting me preview the outcome at lower fidelity, at the cost of time spent on it. The cost/benefit of each type of mockup is going to vary depending on the fidelity of the simulation and the work involved in building the real thing. Four levels of fidelityTime to build versus confidence gained prototypesinterfaces
Four levels of fidelity Suppose we have four levels of fidelity… Rough sketch (on paper or an iPad) Static mock-up (eg. Photoshop or Sketch) Interactive mock-up (eg. Framer, InVision) Working code prototype (HTML/CSS, iOS views) Depending on the feature you’re working on, these levels of fidelity take different amounts of time to create. If you plot them in terms of time to build versus confidence gained, you could imagine something like a per-feature fidelity curve.
Time to build versus confidence gained Show image 0 Show image 1 Show image 2 Take a simple CRUD web UI, where you’re just navigating between screens. It doesn’t take much more time to build the real version than it does to mock it when the design is simple. If you were to build out an interactive mock first, you would end up spending twice as much time in total without gaining much out of it. Contrast that with a complicated Javascript interaction. Or a native iOS feature that requires programmer time to build out. If it takes substantially more time to build the real code version, then it may be smart to do an interactive mockup first.