The relationship between people are unique, especially when we get to work with people of different skillset, different personalities, and even from different culture. But despite our differences, we want to build the best product!
One of our findings from our survey reveals that, working in the software development triangle, PMs seems to be the bridge that connects UX and Engineers but we think that maybe it’s time to start building a bridge!
“Have you come across any specific scenarios/issues working with UX?"
"Mainly if the designer is not sitting with the team. The lack of interaction between the developers and the designer is the most important source of frustration.”
By having an early and frequent communication with engineers, it would made us aware of the potential technical concern, and to put that into consideration before we hand off the prototype .
The way our mindset works can be affected by our workflow. For example, Designers tend to think from users perspective and their journey, getting from point A to B, in optimal scenarios, without errors or edge cases. The frontend engineers start their work by implementing all “components” included the errors states, and often they do not get these specs from the beginning.
Remember things like variable states, discreet interactions, validation styles and all the different measurement and placement variables in-between.
The more detail you cover, the better engineers will be able to bring your design to life.
In the components team, the web technology is packaged in different way.
See what we use in different teams. The way it is used may sometimes affect the scalability and during integration, some technical implication may appears.
In general you can use HTML as basic structure, and add style with CSS, and make it interactive with Javascript.
Framework describes a given structure of "how" you should present your code. Pretty much like a code-template, along some helpers, constructors etc. to solve/simplify a specific problem or bring your architecture in "order". Learn more about Framework and Library here.
Many elements are already experimented and made out there. It will save our time, and sometimes make it more feasible to have some new elements implemented or modified slightly using the libraries or tool out there. Here are some useful tools, libraries and resources for saving time (For interaction designer or web developer).
Designers are usually a heavy user of either iOS or Android, hardly both. It is good to read up some documents on the differences, and how to design efficiently for both platform.
Things to keep in mind when you design for the two major mobile platforms can be found here.
Learn more about what they do, how they work and what what we can do to make their work more efficient.
An interview with Android developer
An interview with iOS developer
Android users expect your app to look and behave in a way that's consistent with the platform.
Google strongly advise you to follow material design guidelines for visual and navigation patterns, and also follow quality guidelines for compatibility, performance, security, and more.
Most Android application uses material design. You can find the design guideline here.
As we do not have tester in Schibsted, it is important for designers and developers to know the fundamental guidelines to the app and here you can find useful checklist to test the design you created if it fits un the Android quality app criteria. You can also check the test procedure here.
Body movin is an After effects plugin that Lottie also uses. It allows us to create transition and animation of components within the app.
The problem is that it’s still experimental and doesn’t support the whole set of animation features that Lottie does. But that looks like a good start.
As an app designer, you have the opportunity to deliver an extraordinary product that rises to the top of the App Store charts. To do so, you'll need to meet high expectations for quality and functionality.
iOS uses human interface guidelines, it explains the design principles and the expectation for quality and functionality.
PaintCode Plugin for Sketch makes it really easy to export your drawings into Swift or Objective-C. Which developer can then use the generated code into their Xcode projects. Alternatively, you can also just upload it to Zeplin as an iOS project, the developers will be able to download from there.
Building animation and transition from scratch is time consuming. Cocoacontrols is an open source library where you and iOS developer can help each other to reuse or tweak an existing components to make development process easier.
Get Inspired