Skip to content
This repository was archived by the owner on May 7, 2025. It is now read-only.

kiwicom/orbit-swiftui

Repository files navigation


Kiwi.com library swiftui-version swift-version swift-package-manager Build

Orbit SwiftUI is a component library that provides developers an easy way of building Kiwi.com’s products.

⚠️ This repository has been archived

As of 7/5/2025, this repository has been archived and is no longer actively maintained.

The code remains available for use and reference, but no new issues, pull requests, or updates will be accepted.
If you are currently using this library, you may continue to do so, but please note that no further development or bug fixes will be provided.

Orbit Mission

Orbit aims to bring consistency to our products and processes.

Orbit is an open-source design system created for specific needs of Kiwi.com.

This library allows you to integrate it into your iOS SwiftUI project.

Requirements

  • iOS 13
  • Xcode 15
  • Swift Package Manager

Installation

Add Orbit package to your project by adding the package dependency:

.package(name: "Orbit", url: "https://github.com/kiwicom/orbit-swiftui.git", .upToNextMajor(from: "0.10.0")),

Documentation

DocC
DocC documentation

The online documentation contains instructions on how to get started with the library as well as examples and pages for individual components.

You can also build the documentation locally in Xcode (Product -> Build Documentation).

App Store

The Orbit Storybook that contains a showcase of Orbit foundation and components can be built in Xcode or downloaded as a standalone app in the App Store.

Download on the App Store

Contributing

Feel free to create bug reports and feature requests via the Issues tab.

If you want to directly contribute by fixing a bug or implementing a feature or enhancement, you are welcome to do so. Pull request review has following priorities to check:

  1. API consistency with other components (similar components should have similar API)
  2. Component variants matching design variants (components should have same properties as design)
  3. Visual match to designs
  4. Internal code structure consistency (button-like components should use consistent mechanism, haptics etc.)
  5. Previews / Storybook consistency (a new component needs to be added to the Storybook)

Feedback

We want to provide high quality and easy to use components. We can’t do that without your feedback. If you have any suggestions about what we can do to improve, please report it as an issue.