Moreover, when they change something, we don’t want to go over the list of colors and manually update them in our Assets. We need a way to import their list of colors into our project.
There is a small problem though: our designers usually work in Figma, not in Xcode. These colors are available through the Interface Builder, or we can instantiate them using the UIColor(named:) initializer. This also lets us have a visual representation of all colors in the application, and verify that they are correct in both themes. This lets us define semantic colors that include variants for light and dark modes, and get the right one without too much hassle. In our project, we try to use named colors defined in our Assets in Xcode. In this first post, we will focus on colors. We are still in the process of adopting it, but we found some interesting aspects that we would like to share with you. It serves as a common language between designers and developers to unambiguously refer to certain items in our software and improve the way we work. But that does not stop there from a developer’s perspective, it also has great benefits, as existing components and interactions can be easily reused.Īs part of our efforts to enhance consistency across GoodNotes, our team has been working on a Design System: a library of tokens and components that we can refer to when implementing new features into the app.
#Change goodnotes folder color how to#
This helps them relate knowledge from previous features in your app, or in the system, and quickly learn how to use new functionality. From a user’s perspective, it is paramount that things that are the same, look the same, and are used the same. These two aspects are what we call UI/UX, and they are not easy to get right, even though, fortunately, the iOS frameworks already give us a very good result with default components.Ĭonsistency is key to achieve a good UI/UX in an app. An important aspect to the success of an application is how it looks, and how easy it is to use.
0 kommentar(er)
