Interested in what’s planned for Orbit in the coming weeks and months? This is a good place to start.
We focus on this in the current quarter.
Sketch introduced Smart Layouts, so we plan to support this great feature with our UI kit. We believe it will be a huge productivity boost not just for UI work but also for maintenance.Estimation: Q3/2019
We have all common components ready, we’re improving their accessibility and tokens coverage and then we will be able to release version 1.0.0.Estimation: Q4/2019
Design teams changed structure to cover features on all platforms, but Sketch UI kit is not ready for it now. So we want to extend it by some components that are available only in Figma.Estimation: Q4/2019
We have all basic stuff for a11y baked in Orbit, now we focus on passing all that into our production.Estimation: Q4/2019
Emails have their own set of components and Orbit should approach them in the same way as we are preparing components to React for front-end teams.Estimation: Q4/2019
We’re discussing how to solve the situation around our UI tooling, and we should be ready for possible switch between tools. It would be great to have this ready at least by 80% of components.Estimation: Q4/2019
We plan to focus on this in 1-2 quarters from now.
The main goal of Abstract was to easily find design when needed – but we have a bit of chaos in branches, commits and structure of Sketch files, so we need to clean it a bit to make designers more effective in their daily work.Estimation: Q4/2019
We want to provide the possibility to easily go through variations of any components, and playground is the best way how to do it.Estimation: Q4/2019
Create a content style guide and voice & tone recommendations for Orbit texts.Estimation: Q4/2019
Currently, we have several components related to List components – some of them are interactive, some with icons, some without them. We plan to refactor them and improve their composability to offer more flexibility for our consumers.Estimation: Q4/2019
Introduce a more systematic approach to design tokens. Merge duplicates and allow easier theming with fewer possibilities of breaking the whole. We want to better support also tokens for specific breakpoints or platforms.Estimation: Q4/2019
We provide ways of composing our components into bigger ones, however, we lack in their better extendability – we want to open our ecosystem a bit more with better event management.Estimation: Q1/2020
We want to provide an overview of Orbit adoption across all our projects, with the list of used components, adopters and mostly to provide information to maintainers about possible breaking changes.Estimation: Q4/2019
Items and ideas considered to do, without any commitment. We’ll see what the priorities will be once we’ll get there.
After rapid introduction of many form elements, we noticed some inconsistencies in naming, composabilitY and clear purpose of several form components. We want to improve these aspects, as well as introduce better guidelines on forms in general.Estimation: not set
We are slowly introducing more complicated interactions and transitions, we will need to write some guidelines for animations so it’s consistent behavior across the product and works together.Estimation: not set
The main goal: have components developed also for iOS and Android so we support better workflows and full Orbit adoption for our mobile team.Estimation: not set, currently working on React Native
We currently have two designs for forms – for desktop use and for mobile apps. We want to try to find one way how to display it or at least match visual style for components where we can do it.Estimation: not set
We have a lot of colors defined for our white labels, we are duplicating #hexa codes and it’s a mess a little. The goal is to clean it, make the system out of it and improve the experience of white labels by defining colors that can & shouldn’t be changed.Estimation: not set