Proof of Concept - Building your designs
At some point in a designer’s career, the age-old question is asked: "Should designers code?" My direct answer for people who design software interfaces is yes. This is a belief held my entire career. Despite my stance, I don't like the question. It might be the wrong question to focus on and variers on who is asking it. Designers feel like they are doing multiple jobs, so if someone outside our practice prowokes the question, it feels like we're being asked to do more without being rewarded for the work. At its core, design is taking an idea and making it tangible. Building your designs is a continuation and extension of that tangibility. Ignore the question of whether designers should code and look at it as we should build our designers. Designers build. The fidelities of buildingBuilding your designs doesn’t assume production code. Less than 5% of the code I've written in my career made it to production (that’s a good thing), but 100% of it was considered in the software development process. One of my favorite use cases to build my designs is to quickly navigate through the intrface flow. When I use to work on iOS apps, my favorite method of building iOS prototypes was a simple Xcode project using UIStoryboard¹. Storyboards (as the name implies) made it easy to add interface elements in views, connect the views to have a first look at the experience. I’d compile the project and put it on a test iPhone, hand it to the developers for us to walk through the experience. Low-fidelity builds invoke high-fidelity questions. Even in the first run we could have a clear discussion on trade-offs and upcoming design challenges. I’d take the feedback and update the Product Requirements Doc (yes, designers should write PRDs). Here is a video demo of the prototype I built. It’s all built in storyboards with a bit of Swift code to detect the logic. It did not take very long to build either! This is an example of with a little bit of technical acumen you can put something very functional together. There are some designers out there who are truly unicorns in the craft—able to design and write code, even at the production level. They’re often called Design Engineers today, and I think they will be the most sought after role this decade. Building storyboards and UI flows can lead to prototypes, proof of concept, and the insights needed in software implementation. Comprehension of materialsWhen bringing a building or structure to life, interior designers work closely with architects—a similar relationship between software designers and engineers. Interior designers do not focus on architecture but the good ones have intimate knowledge of the considerations and methods of architecture to ensure the design vision can come to life. They may not be the ones building the blueprints, but interior designers understand the engineering design decisions that influence their design. When a sculpture creates a bronze statue, comprehension of the materials is not only the temperature the alloy needs to be heated to pour into the mold. What is the patina effect over time that might change the look of the sculpture? What is the weight and durability of the output? How will people maintain the piece years down the road? Though software is a different process than creating a physical object, there are similar considerations in the interface implementation and maintainability of the codebase. Understanding the build materials fosters accessible design. If you care about accessibility, buildings your designs will make you even more considerate of it. It'll force you to think about the different states and properties of an interface. Running a built interface through a screen reader builds more empathy than a representation of an interface. Understanding the production lineBuilding and shipping software is like other product development processes. There is a production cycle that usually can be improved. One added benefit of building your designs is understanding how software is made. There is a slew of steps before you should ship: implementation, quality assurance, systems testing, and more. Going through this process yourself allows a clear picture on what happens to the design through implementation. You’ll better understand bottlenecks and have a stronger sernse of what considerations will need to be made as your design gets pushed through. Getting acclimated to buildingIf you’ve never built software with code, getting started can feel intimidating. Fortunately, the code barrier is lowering every day, making it more approachable and accessible to do so. Building is not a process, it's an action of transformation, and it matters less on how you build it. When learning a new skill, I recommend finding the laziest way possible to build confidence. I used to take screenshots and reproduce them in Photoshop to build up my interface design skills. Here are some ideas to accelerate your comfort with the material of software:
As you get more comfortable, you’ll be able to write more code from scratch. Remember, these skills take years to develop so focus on daily progress and small wins. Building empowersIt’s heartbreaking to see a designer spend all this time working on screens and it never coming to life. Build your designs because you will make your idea tangible—don’t do it for others. It’s not, “designers should do this.” It’s, “I will do this.” Someone once said to me, "When you build your designs, it expands your influence in decision-making. Why would you opt out of those as a designer?" I think about this a lot. Great software designers think of design from idea to software. We proclaim this a lot yet don't practice it. Building your designs makes you a better designer. Designers build. Week 06 recap
Hype links
A great reminder by Dr. Julie Gurner—going to do this for Week 07.
Job opportunities
1 This was way before SwiftUI existed You're currently a free subscriber to Proof of Concept. For the full experience, upgrade your subscription. |
Older messages
Artists, galleries, and patrons
Sunday, February 4, 2024
Issue 180: How are art and tech scenes mirror each other
The work loadout for travel
Sunday, January 28, 2024
Issue 179: What's in my bag (work edition)
Inspiration Notes - Hideo Kojima's "Making the Impossible Possible"
Sunday, January 21, 2024
Issue 178: How a GDC keynote applies to Product Design
How experienced managers should think about career opportunities
Wednesday, January 17, 2024
Issue $P2: From high volume to high touch searches
Bring Your Own Abstraction (BYOA)
Sunday, January 14, 2024
Issue 177: When personalized workflows converge in the same workspace
You Might Also Like
The Problem With Using Social Media as Design Education
Tuesday, May 7, 2024
View in your browser | Update your preferences ADPro Image may contain: People, Person, Accessories, Bag, Handbag, Food, Meal, Adult, Clothing, Hat, Glasses, Fun, and Party Twenty-five days were left
#455: CSS
Tuesday, May 7, 2024
CSS Masonry Layout, Self-Modifying CSS Variables and Hanging Punctuation Issue #455 • May 7, 2024 • View in the browser Smashing Newsletter Dobryi vechir Smashing Friends, When I first encountered CSS
🤯 Immersive Admin Dashboard Designs + 🏆 Challenge Updates
Tuesday, May 7, 2024
Stay Up-to-Date With UpLabs' Latest Design News 🎨 Firstly, let's congratulate Rahul Parmar, the winner of our latest 👾 ChatGPT Redesign Challenge! Congratulations!! Secondly, the end of April
Web Components, Conditional Styling, Popover API, color-mix(), Product Designers
Tuesday, May 7, 2024
The 5 best design links, every day. Curated by a selection of great editors. Email not displaying properly? View browser version. Sidebar May 7 2024 Map of the web graph.henryn.ca A visualization of
Map of the Web, JSR Registry, Presidential Campaign a11y, Age of Average, CSS Specificity
Tuesday, May 7, 2024
The 5 best design links, every day. Curated by a selection of great editors. Email not displaying properly? View browser version. Sidebar May 6 2024 Map of the web graph.henryn.ca A visualization of
How we do UX retreats at Balsamiq (+ steal our agenda!)
Monday, May 6, 2024
Inside our UX group retreat ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Accessibility Weekly: #395: Why Are My Live Regions Not Working?
Monday, May 6, 2024
May 6, 2024 • Issue #395 View this issue online or browse the full issue archive. Featured: Why are my live regions not working? "Live regions have a reputation for being "flaky" and
Writing a POV Doc
Sunday, May 5, 2024
Issue 193: Share what you care about at scale ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
It's Officially Show House Season
Thursday, May 2, 2024
View in your browser | Update your preferences ADPro Showing Up, and Showing Off One of the traditions design aficionados look forward to the most each year is the return of decorator show houses. In
Zelman Meats, AI Feedback Loop, Figma Variables, CSS Masonry, Passkeys
Thursday, May 2, 2024
The 5 best design links, every day. Curated by a selection of great editors. Email not displaying properly? View browser version. Sidebar May 2 2024 Zelman Meats logo by Red Dot Studio logodesignlove.