small_Fcsqb5pWQAAzPIK.jpeg

thumbnail_Fcsqb5pWQAAzPIK.jpeg

Adobe acquires Figma, cue the memes 🤪

large_Crossover Series NFTs.png

medium_Crossover Series NFTs.png

small_Crossover Series NFTs.png

thumbnail_Crossover Series NFTs.png

From Photography to NFT Art: Twisted Digital Landscapes with Nate Hill

From Design System to ‘NFT Design System’: Creating TinyFaces

Neurodiversity and Inclusion: Choosing Kinder Design

Published on <a href="https://blog.prototypr.io/what-having-apple-as-a-client-taught-me-9e3e671acd60?source=rss----eb297ea1161a---4">| Prototyping: From UX to Front End &mdash; Medium</a> Shay Ho 
I was lucky enough to I’ve worked for Apple, one of the biggest brand in the world. It was a bit of a shocking but proud moment of my career as a designer.
As you could probably guess, it wasn’t an easy job, not that I couldn’t handle it, but it’s the stress, the workload (my worst day was 18 hours) and the disciplines involved. I was proud that I was an organised person, a tidy freak even, the job made it worse (or better ¯\\_(ツ)_/¯). Of course I learned a lot in the course of those 2 years.
<img alt="" src="https://cdn-images-1.medium.com/max/500/0*_-McYguazpej1l78.png">[Image description: A skeleton in a dining room with a glass of wine. Text says “When you finally get home after a long day at work. Wiped out.”
<h3>1. Organisation is key.</h3>
“Normal people” (non-designer, or even some, possibly graduates, designers) think design is only creativity and not about being tidy. Who cares if you have a messy work environment, right? We just need to be free and creative, right? But as a professional of the craft, organisation clears your schedule of looking for files, writing documents, handoffs or anything that is not design but very important. Thus, you guessed it, more time to create.
Imagine if you have 30 screens to create in Sketch, and you don’t start organise your document from the beginning, you’ll have a bad time trying to make sure those buttons are the same colours.
Or if you use Photoshop and you have 30 screens with a million documents to read, assets to use, good luck locating things after the 3rd screens.
So yeah, you’d better kick those habits soon.
Tips: Split your files into different folders. Mine are: Assets, WIP and _exports usually. I may have more with bigger projects.
<img alt="" src="https://cdn-images-1.medium.com/max/672/1*zd-RoHDNhOoK7saE9DSONQ.png">[Image description: File organisation]
<h3>2. Tidy up along the way.</h3>
So you started a project, everything is looking good but you didn’t bother tidy up those odd pixels, or your artboards everywhere. Oh boy, you’re gonna a bad time. Why? Because unless you’re fresh out of uni and never know about what handoffs are, or you work as a freelancer your whole life, you’re probably going to have to help your engineers do their jobs. No one likes people who dump Sketch or Photoshop files with no specs or off pixels. And you don’t want to do it at the end of your project either.
I know it may sound tedious but it’s part of the job (not to me though, I looooooove tidy documents).
Tips: There is a plugin in Sketch call <a href="http://utom.design/measure/">Sketch Measure</a> that will speed up your process and remind you to tidy up your file.
<h3>3. Less is more.</h3>
This is not a new thing. But it’s not an easy thing either. When I was younger, I tend to do too much and I never knew when to stop. Working for this client forced me to do just that. The devil is in the details, one animation can be so tiny you barely see it but it adds to the charm of it all.
<img alt="" src="https://cdn-images-1.medium.com/max/1024/0*48E_p-TOCru2M-gR.">[Image description: <a href="https://www.zazzle.com/keep_it_simple_stupid_poster_print-228891179017494377">style poster of “KISS, Keep it simple stupid”</a>]
Cliche, I know, but ask yourself everytime you do something “Does it serve a purpose? Does it make my design better? Does this feature help my users?”
Tips: Atomic Design helps me a lot with this. I have bricks to build from instead of throw everything in to the artboard and call it a day. You can also read more about <a href="https://www.google.com.au/search?dcr=0&amp;ei=MrbBWoGbH4Kn8QXXxodQ&amp;q=design+system&amp;oq=design+system&amp;gs_l=psy-ab.3..0i67k1j0i7i30k1l4j0l2j0i7i30k1l2j0.4134.4134.0.4374.1.1.0.0.0.0.214.214.2-1.1.0....0...1c.1.64.psy-ab..0.1.212....0.n_BmplgWKKI">Design System</a> to expand your design horizon.
<img alt="" src="https://cdn-images-1.medium.com/max/676/0*TlcLCyoo4iKp79Bf.gif">You can also purchase UI kits or Design systems to speed up your process [Image description: A GIF of <a href="https://cabanadesignsystem.com/">Cabana Design System by kissmyui</a>]
<h3>4. Learn to code.</h3>
This has been a popular topic lately. No, I’m not saying you have to understand all the languages and frameworks (unless you want to), but understand the basics helps.
Firstly, you’ll know what are the limitations that you have to work with so you don’t have to iterate and iterate and iterate. No, it’s not going limit your creativity. In fact, having limitations help you focus and you can solve the real problems for the users.
Secondly, you can speak your engineers’ language. So instead of trying to explain what “leading” is and you can say line-height and everyone is happy.
Tips: Make friends with a couple of software engineers, or at least be friendly with them. They can probably learn something from you too 😉
<img alt="" src="https://cdn-images-1.medium.com/max/474/0*XQ7hGtOWmOIaIaua.">[Image description: A meme of Buzz Lightyear saying “Coding, coding everywhere” to Woody from Toy Story]
I know these seem obvious but they can be bad habits that hard to break. Did you have any similar experience where you had to change your work approach? Let me know your thoughts.
Shay is a Vietnamese UX designer based in Sydney, Australia.
<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ff51076%2F&#038;image=https%3A%2F%2Fe.enpose.co%2F%3Fkey%3DdRXnS9Gplk%26w%3D700%26h%3D425%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%252F%253Fenpose&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0"><a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&amp;referrerSource=full_rss&amp;postId=9e3e671acd60" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou">
<hr>
<a href="https://blog.prototypr.io/what-having-apple-as-a-client-taught-me-9e3e671acd60">What having Apple as a client taught me</a> was originally published in <a href="https://blog.prototypr.io">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.

What having Apple as a client taught me

What having Apple as a client taught me

Top Stories