Interested in what’s planned for Orbit in the coming weeks and months? This is a good place to start.

Roadmap contains delivery estimates only in quarter scope. For a more detailed overview of what is already designed and in what state, visit component status or Road to 1.0.0.

What's next?

Last update: 1st August 2019

Current term

We are focusing on this in the current quarter.

Release stable version of Orbit components

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: Q3/2019

Support native apps in Sketch UI kit

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: Q3/2019

Account in React Native

We are extending Orbit to React Native and React Native Web. That means not just prepare tokens, but also prepare components. This is just another step to support multi-platform components with Orbit. We will be directly supporting components from Account.

Estimation: Q3/2019

Improve Orbit.Kiwi documentation

Based on a lot of feedback we've got on Orbit documentation, we plan to add some new features to help people to navigate through docs better and add examples of component usage.

Estimation: Q3/2019

Support accessibility adoption

We have all basic stuff for a11y baked in Orbit, now we focus on passing all that into our production.

Estimation: Q2-Q3/2019

Launch Orbit.Kiwi 1.0

We are extending component documentation with live examples and we're hiring a new content writer to help us with writing & reviewing content. We are also changing the way we communicate Orbit to the outside world – going full open source.

Estimation: Q3/2019

Extending Orbit for event pages

Every year, we organize a lot of events like hackathons, educational weekends, conferences... Everything is made custom, it costs us a lot of money and time; also the quality is questionable. We want to improve it by introducing event templates in Orbit.

Estimation: Q3/2019

Launch Orbit Dashboard

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

Near term

We will focus on this in 1-2 quarters from now.

Add calendar to Orbit

It should support all travel related features – single date, range, drag&drop.

Estimation: Q3/2019

Extend Orbit to emails

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: Q3/2019

Improve design tooling

We currently support Sketch and Figma workflows, which is generating some unneeded duplications. The goal is to solve it somehow, so we can focus on the best support behind consistent tooling.

Estimation: Q4/2019

Create guidelines for Sketch & Abstract

The main goal of Abstract was to easily find design when needed – but we have a bit of chaos in branches, commits and Sketch structure, so we need to clean it up.

Estimation: Q3/2019

Create content style guide

Create a content style guide and voice & tone recommendations for Orbit texts.

Estimation: Q3-Q4/2019

Extend Orbit Themer

We should support all theming features that Orbit provides – design tokens, all colors, etc. We should also improve usability and understandability of the whole page.

Estimation: Q3/2019


Items and ideas considered to do, without any commitment. We'll see what the priorities will be once we'll get there.

Improve theming possibilities

Introduce a more systematic approach to design tokens, mostly for sizing and spacing. Merge duplicates and allow easier theming with less possibilities of breaking the whole. It will also require more advanced testing.

Estimation: not set

Refactor form components

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

Guidelines for animations

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

Develop Orbit components for native mobile

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

Synchronize form inputs across platforms

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

Brand color cleaning

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