Expo SDK 55

Today we're announcing the release of Expo SDK 55. SDK 55 includes React Native 0.83 and React 19.2. Thank you to everyone who helped with beta testing.

Expo Go for the App Store and Play Store will remain on SDK 54 for a short window of time following this release, and the default project created with npx create-expo-app will continue to use Expo SDK 54 for consistency.

The Expo Go app is our tool for getting started quickly, it's an educational tool to help you learn to build on mobile. We encourage you to take advantage of this transition period to migrate your project to using a development build, which provides you with everything that you need to build an app that you ship to stores.

During this period, you can install Expo Go for SDK 55 from Expo CLI directly on Android devices. For iOS, you can use the TestFlight External Beta or the new eas go command to create an Expo Go build for SDK 55 and upload it to your own TestFlight team. To create an SDK 55 project, use the --template default@sdk-55 flag with create-expo-app.

The default template has been redesigned with a focus on native platform conventions and an improved project folder structure:

• Uses the Native Tabs API for a platform-native tab experience on iOS and Android, with a responsive web-optimized layout for browsers.
• Refreshed design for a better out-of-the-box experience.
• New /src folder structure, so application code now lives in /src/app instead of /app, better separating your code from project configuration files.

To use the new project template:

As explained in the SDK 54 release notes - “SDK 54 is the final release to include Legacy Architecture support”. In other words, you will not be able to use the Legacy Architecture in SDK 55 projects and later. Accordingly, the newArchEnabled config option has been removed from app.json. Learn more in the “React Native’s New Architecture” guide.

Hermes v1 represents a huge step forward for the engine, showing early signs of meaningful performance improvements across various scenarios, and shipping better support for modern JavaScript features (ES6 classes, const/let syntax, async/await). You can try it out in your app with the useHermesV1 field in expo-build-properties.

It’s important to note that using Hermes v1 in Expo SDK 55 / React Native 0.83 requires building React Native from source, which significantly increases native build times. This tradeoff might be worth it for your app, give it a try, find out, and let us know!

{
  "expo": {
    "plugins": [
      [
        "expo-build-properties",
        {
          "buildReactNativeFromSource": true,
          "useHermesV1": true
        }
      ]
    ]
  }
}

You will need to override the hermes-compiler version to use the Hermes V1 compiler. Depending on your package manager, this field may be named differently. With npm, pnpm, and bun, the field is named overrides; for yarn, it is resolutions. For example:

{
  "dependencies": {},
  "overrides": {
    "hermes-compiler": "250829098.0.4"
  }
}

The Hermes bytecode diffing feature in expo-updates and EAS Update is an optimization that significantly reduces update download sizes for Hermes-compiled JavaScript bundles. Instead of downloading complete Hermes bytecode files for each update, the expo-updates client can request and apply binary patches (diffs) to the previously installed bytecode files.

This means your updates will be downloaded more quickly by end-users, and that each update will use less bandwidth. That all translates to faster update adoption rates and more updates available within the bandwidth of your EAS plan. It’s estimated that diffs will result in an approximately 75% reduction in Hermes bytecode and JavaScript download times on both Android and iOS.

{
  "expo": {
    "updates": {
      "url": "https://u.expo.dev/[your-project-id]",
      "enableBsdiffPatchSupport": true
    }
  }
}

This feature is opt-in for SDK 55, and we’ll turn it on by default in SDK 56. To enable it in your project today, refer to the enableBsdiffPatchSupport property documentation for information on the app.json config or iOS/Android native config options. You can confirm that bundle diffs are being served from the Update Details page. Open the Update Group you published, then select the platform you want to inspect.

If you’d like to try it with your own custom updates server, refer to this branch on expo/custom-expo-updates-server. Note that we’re prioritizing polishing up the experience with EAS Update, and we will improve the custom updates server reference at a later date.

An Expo Module can expose plugins and commands to the Expo CLI which will be made available in the [SHIFT] + M menu - these actions can now be automatically installed in the Expo MCP Server.

Additionally, you can now query EAS with the Expo MCP - so you can ask questions like “why did my most recent build fail?”. You can also query TestFlight crashes and feedback (if you have your ASC key associated with your Expo account, which is used typically during EAS Submit), so you can ask your agent of choice to “investigate the most recent crash reports and feedback from testflight” and watch it work.

The expo/skills repository is the official collection of AI agent skills from the Expo team for building, deploying, and debugging robust Expo apps. We primarily use Claude Code at Expo and skills are fine-tuned for Opus models. But you can use these skills with any AI agent.

We have found these skills to be a great complement to the MCP, and they help Claude Code work with Expo apps better than ever before. Try them yourself and give us feedback on how we can make them even better! We also welcome pull requests!

Be sure to check out the upgrade skills (installation instructions), which we recommend in the upgrading section to help you with upgrading to SDK 55.

Note: there are a lot of “expo/skills” being created by the community, which is great! The only skills that we currently officially endorse and plan to maintain/update are the skills you find in our expo/skills repo.

SDK 55 improves the support for Brownfield apps and introduces a new isolated approach to brownfield integration via the new expo-brownfield package. You can now choose between integrated and isolated when developing your Brownfield project.

• Integrated: React Native code lives inside your existing native project, ideal for teams iterating on both together.
• Isolated: package your React Native app as a native library (AAR/XCFramework) that native developers can consume without needing a Node.js environment.

The package includes a config plugin, CLI for building artifacts, and APIs for bi-directional messaging between your native and Expo apps. We've also improved support for packages like expo-dev-menu with SwiftUI support and standalone usage.

Learn more in the Brownfield documentation.

• New Colors API: add dynamic Material 3 styles to your Android app and adaptive colors on iOS.

Notice that the colors in the app adapt to the operating system in these screenshots.

• New Apple Zoom transition: we’ve added support for interactive shared element transitions on iOS using the native zoom transition and gestures. This is currently an Apple-only feature, and it is enabled by default. Learn more.
• New Stack.Toolbar API: UIToolbar API for iOS apps that provides access to APIs for building menus and actions. It’s currently iOS-only, and we plan to add support for similar Android APIs in the future. Learn more.

This UI pattern is a useful alternative to tabs when you want buttons at the bottom of the screen that need to perform actions or open menus rather than navigate between entire screens.

• Experimental SplitView support: this has been something we have wanted for ages, and much needed in React Native. Learn more about SplitView.
• Experimental support for footers in form sheets on Apple platforms: useful for adding action buttons or confirmation prompts to modal sheets. Learn more in the API reference.
• Default safe area handling in native-tabs layouts on both iOS and Android: so you no longer need to manually handle safe area insets in tab layouts. Learn more about safe area handling.
• Screen's synchronous layout updates activated by default: reducing layout jumps during navigation transitions. Learn more in #42154.
• New default configuration for form sheet header on iOS 26+: your form sheets will automatically adopt the Liquid Glass design language with no code changes. Learn more in #42741.
• Xcasset icon support in native tabs and header items / bottom tabs: you can use your Xcode asset catalog icons directly in tabs and headers, with renderingMode support.
• New NativeTabs and Stack props: added listeners and screenListeners props to NativeTabs for responding to tab events like focus and blur, asChild prop to Stack.Screen.Title, and disableTransparentOnScrollEdge to NativeTabs.Trigger.
• react-native-screens upgraded to 4.23.0: bringing improved modal presentation and native screen lifecycle handling. See the changelog.

We are working towards a stable release in mid-2026, and the improvements in SDK 55 represent a huge improvement in its capabilities already. We’ve also added skills to expo/skills to make it easier to get started with Expo UI for both SwiftUI and Jetpack Compose.

We have promoted our Jetpack Compose API from alpha to beta. As a test case for it, we created a clone of WikiReader by @nsh07: expo/wiki-reader.

• Reworked to a functional DSL pattern: compose views are now defined with View("MyView") { props -> } instead of class-based definitions. A huge thank you to @kimchi-developer for the incredible migration PR that refactored all leaf components to the new pattern.
• Many new Material3 components (#42734): Card, LazyColumn, ListItem, PullToRefreshBox, FlowRow, Surface, Icon, DockedSearchBar, FilterChip, ToggleButton, RadioButton. Also added ModalBottomSheet, Carousel, IconButton, and wavy progress indicators. Thank you to all the external contributors who helped add these components! We don't aim to wrap every Material3 component — we added what we needed for the wiki-reader clone and will continue adding more based on demand, so let us know what you need!
• Modifiers support: apply SwiftUI-like modifiers to your Compose components. For example: <Box modifiers={[size(100, 100), background(Color.android.dynamic.primaryContainer)]} />. Includes scoped modifiers with Row/Column-specific modifiers (weight, matchParentSize). Learn more about @expo/ui/jetpack-compose/modifiers.
• <Icon> component now natively renders Material Symbols XML vector drawables with tinting, sizing, and accessibility support — download icons as XML drawables and use them with <Icon source={require('./icon.xml')} tintColor="red" size={24} />. This aligns with the modern Android development workflow of using Material Symbols XML vector drawables. Learn more from the Icon component.
• matchContents for Host for auto-sizing compose views, and Host.colorScheme for dynamic theming — equivalent to the SwiftUI Host API, bringing feature parity across platforms.
• leadingIcon/trailingIcon support for Button and ContextMenu and custom button shapes.

Learn more in the Jetpack Compose documentation.

We've updated @expo/ui SwiftUI component APIs to more closely match SwiftUI's. If you're familiar with SwiftUI, the Expo UI equivalents should now feel more familiar. We’re still in beta, and accordingly there are a number of breaking changes:

• Breaking API renames to match SwiftUI conventions: DateTimePicker → DatePicker (now supports range and custom labels), Switch → Toggle, CircularProgress/LinearProgress → ProgressView. Section, Form, Button, and Slider APIs also updated. See the SwiftUI docs for the new APIs.
• New components: ConfirmationDialog, ScrollView.
• New modifiers: contentShape() for defining tappable areas independently from visual bounds, monospacedDigit for stable number layouts in timers and counters, per-axis scaleEffect for patterns like inverted lists, and ignoreSafeArea for Host.
• Markdown support in the Text component.
• Support for custom SwiftUI views and modifiers: since we can't cover every SwiftUI view and modifier, we've made expo-ui extensible — you can create your own custom components and modifiers. Learn more.

The hot-chocolate showcase app has also been updated to SDK 55 and the latest Expo UI APIs. Check it out for an example of building with SwiftUI in Expo.

As of SDK 55, all Expo SDK packages use the same major version as the SDK. For example, the version of expo-camera that is compatible with SDK 55 is ^55.0.0. This makes it easy to identify at a glance that your Expo SDK packages are in fact intended for the SDK version you are using. It also accurately reflects that we do not intend for packages to be compatible across different SDK versions.

Expo Modules Core is the foundation for building native modules with a modern, unified API across iOS and Android. We use it for all of our modules, and we are always investing in making it the best tool to reach for when you need to extend the native capabilities of your app. Some of the improvements in SDK 55 include:

• Adopted Swift 6 language mode: if you maintain native modules, your code will now be checked for data races at compile time, helping guarantee thread safety.
• Added ArrayBuffer support: enabling efficient binary data transfer between JavaScript and native code — useful for audio, image, and file processing. Learn more in these pull requests: #39943, #41404, #41415, #41548. Documentation coming soon.
• Added StaticFunction and StaticAsyncFunction to Class in modules API: allowing you to call functions on the module class itself without creating instances. Learn more in these pull requests: #38754, #39228.

• Improved dev server startup screen: the startup screen has been tweaked and got polished a little. It will now try not to cut off the QR code in small terminal windows, smaller QR codes will be displayed in terminals that support the new rendering mode we added (Alacritty, Ghostty, Kitty, Windows Terminal), and rendering bugs that prevent a working QR code from displaying have been fixed.
• Environment file support via @expo/env: updated to rely on Node.js’ built-in parseEnv support. Dotenv support shouldn’t have noticeably changed and still supports expanding environment variables.
• Reliable first-time local network access in development builds: we’ve added Apple Bonjour support for iOS + expo-dev-client in development builds in order to reliably request local network permissions before any request is made to a dev server by React Native. This works around an issue caused by a lack of a public API on iOS for requesting or querying local network access, and fixes a longstanding issue on iOS development builds where the app would hang or fail to load apps from your dev server on the first launch. We’ll continue investigating how to improve the experience on Android.
• Dynamic app config loading: loading of dynamic app config files, such as app.config.js, has been updated to align with Node.js’ support of module loading. We now experimentally allow using .mjs, .cjs, .cts, and .mts for dynamic config extensions.
• Experimental new Log Box on native: on web the new experience is enabled out of the box, for mobile development add EXPO_UNSTABLE_LOG_BOX=1 and rebuild the native application. The new interface doesn’t work in Expo Go yet. Try it out and let us know your thoughts!

expo-widgets enables the creation of iOS home screen widgets and Live Activities using Expo UI components, without writing native code. It provides a shared-objects-based API for creating and updating widget timelines, starting and managing Live Activities, and listening for push-to-start tokens. Layout can be built using @expo/ui components and modifiers — this is the main distinction between expo-widgets and Voltra. Learn more about expo-widgets.

Performant background blurring has been a pain point for Android developers for a long time — and that includes React Native developers targeting Android. In expo-blur, blurring on Android was hidden behind the experimentalBlurMethod due to high performance cost of rendering the blur. Starting with SDK 55, expo-blur uses the much more efficient RenderNode API on Android 12 and newer. This allows developers to add background blurs to views at a low performance cost.

Support for the new blur method required us to change how the Blur API works. You will now have to specify a <BlurTargetView> wrapper for the blurrable background content. If you don’t want to migrate to the new API just yet and need background blurs only for previously supported platforms, you can keep your current implementation as the introduced changes are non-breaking. Learn more.

A special thanks goes out to Dima Saviuk — these changes were possible thanks to work on Dimezis/BlurView, which we use for blurring on Android.

expo-sharing now provides a highly requested feature out-of-the-box: first-class support for sharing data into Expo apps. This will be possible thanks to a config plugin, which adds a share-extension app target on iOS and appropriate intent-filters on Android. Sharing requests are delivered via deep links, allowing you to easily handle them in JavaScript.

Thank you, Maxi Ast for your work on MaxAst/expo-share-extension! If you’re looking for this feature and want to use a library that has been battle tested in production, expo-share-extension may be a good option for you. This feature in expo-sharing will be marked as experimental in SDK 55.

Learn more about adding the ability to share content from other apps to your app.

• Expo Go: the UI has been completely revamped to align closely with the expo-dev-client changes that we made in SDK 54, and to improve the Hermes debugging experience. This work is a foundation for us to build on in upcoming cycles as we invest more in the user experience of both Expo Go and expo-dev-client. Let us know if we missed any details that are important to you!
• Expo Web: we re-wrote the error overlay, added alpha support for server-side rendering, and have shipped experimental data loaders.
• expo-contacts/next, expo-media-library/next, and expo-calendar/next: new object-oriented APIs for easier and more granular management of contacts, events, and media. Makes it simpler to modify data by using SharedObjects to manipulate them directly rather than passing around IDs. We’ve also added more powerful queries, among other features! Links: Contacts, MediaLibrary, and Calendar.
• expo-notifications: updated to the latest Android Firebase notifications dependency. Several important fixes including background tasks not executing, crash in NotificationForwarderActivity on Android 11/12, FCM intent origin validation, and custom sound existence validation. Refer to the breaking changes section below for more information. Learn more in the expo-notifications API reference.
• expo-audio: the new version includes support for lock-screen controls, background audio recording, playlist support on all platforms (iOS, Android, Web), native preloading (iOS, Android, Web), reworked Android foreground service handling, shouldRouteThroughEarpiece on iOS, and expanded web support including metering, recording input selection, media controls, and audio sampling. Learn more in the expo-audio API reference.
• expo-sqlite: the new SQLite Inspector DevTools Plugin lets you browse and query your app's database in real time. Also added a tagged template literals API for writing type-safe, parameterized SQL queries inline — for example, await db.sql`SELECT * FROM users WHERE age > ${age}`. Parameters are automatically bound, preventing SQL injection.

• expo-crypto: added support for AES-GCM encryption and decryption. Learn more in the expo-crypto API reference.
• expo-camera: added video stabilization mode when recording, screen flash for the front camera on Android, and an option to opt-out of including the barcode scanner APIs in order to reduce your app size. Learn more in the expo-camera API reference.
• expo-web-browser: added auth universal links callback support, and fixed an Android issue where the browser would close after the app was backgrounded. Learn more in the expo-web-browser API reference.
• expo-video: added seekTolerance and scrubbingModeOptions for better scrubbing performance. Picture-in-Picture has been refactored on Android to support handling multiple VideoViews. Added averageBitrate and peakBitrate fields to the video track information. Audio and subtitle tracks now include name, isDefault, and autoSelect fields. Added PlayerBuilderOptions and buttonOptions for VideoView on Android. You should see performance improvements on iOS thanks to loading a larger part of the video data asynchronously. Learn more in the expo-video API reference.
• expo-image: supports HDR images on iOS, can now render SF Symbols, and includes Android cookie support for authenticated image requests.
• expo-server: new package that has replaced @expo/server during the lifecycle of SDK 54. It exposes adapters for server runtimes and hosting providers, making it easy to deploy your Expo app's server-side code to different environments. Learn more in the expo-server API reference.
• expo-file-system: added an append option to write methods for appending data to existing files.
• expo-location: iOS now includes accuracy authorization in the permission response, letting you know whether the user granted full or reduced accuracy.
• expo-maps: added a user interface style option for Apple Maps on iOS, letting you force light or dark map appearance regardless of the system setting.
• create-expo-module: now supports non-interactive mode, making it possible to scaffold new modules from AI agents and CI pipelines without requiring interactive prompts.
• Upcoming minimum iOS version bump: we plan to bump the minimum iOS version from 15.1 to 16.4 in SDK 56. The minimum iOS for SDK 55 is still 15.1. See the platform version compatibility table.

• Deprecated removeSubscription functions exported from several Expo modules: switch to subscription.remove(), where subscription is the object returned when registering an event listener.
• expo-video-thumbnails: deprecated in favor of generateThumbnailsAsync from expo-video. Not receiving patches and will be removed in SDK 56.
• expo-video: deprecated track bitrate field in favor of averageBitrate and peakBitrate: #41532.
• expo-navigation-bar: most methods deprecated and no-op'd now that edge-to-edge is mandatory on Android — background color, border color, behavior, position, and button style APIs no longer have any effect. The androidNavigationBar app.json config is also deprecated; use the expo-navigation-bar config plugin instead: #43276.
• expo-status-bar: deprecated backgroundColor, translucent, and networkActivityIndicatorVisible props and their corresponding setter functions — these are no-ops with edge-to-edge. The androidStatusBar.backgroundColor and androidStatusBar.translucent app.json properties are also deprecated; use the expo-status-bar config plugin instead: #43276.
• Refer to the CHANGELOG for a full list of deprecations.

• Following the deprecation and a warning, the notification configuration field was removed from the app.json schema. Specifying a notification entry will throw an error in prebuild - migrate to the expo-notifications config plugin.
• Attempting to use push notifications in Expo Go on Android will throw an error. Until now, this was a warning. We first informed about the planned removal in the SDK 53 release post. To use push notifications, migrate to a development build.
• App config evaluation toolchain changed. app.config.ts files are now transpiled with your installation of TypeScript, rather than a separate internal tool. If you notice any differences to prior SDK releases, open an issue.
• expo-av was removed from Expo Go because it has been replaced by expo-video and expo-audio. Additionally, expo-av is no longer receiving patches and may not continue working in your apps as a result.
• edgeToEdgeEnabled removed from app.json config: edge-to-edge is now mandatory when targeting Android 16+. #42518.
• expo-router: the reset prop in headless tabs has been renamed to resetOnFocus: #40349.
• expo-blur: experimentalBlurMethod prop renamed to blurMethod: #39996.
• expo.experiments.autolinkingModuleResolution is now enabled by default in monorepos: if you're having issues with dependencies during the upgrade, we recommend trying to enable it to see if it resolves your issue. Learn more in the "Work with monorepos" guide.
• The fast resolver and the EXPO_USE_FAST_RESOLVER have been removed: the fast resolver was already the default — there's now just one resolver implementation, and no action is needed.
• experiments.reactCanary flag removed: React 19 is now the baseline, so the flag is no longer necessary.
• Refer to the CHANGELOG for a full list of breaking changes.

• Minimum Xcode bumped to 26. EAS Build uses Xcode 26.2 by default for SDK 55.
• Minimum Node.js version increased. Expo's Node.js version support tracks LTS versions and also aims to support the latest version. Supported versions for SDK 55 include: ^20.19.4, ^22.13.0, ^24.3.0, and ^25.0.0.

Try using our upgrade skills (installation instructions) with Claude Code, or a similar tool of your choice, to upgrade your app.

Here's how to upgrade your app to Expo SDK 55 from 54:

• Upgrade all dependencies to match SDK 55:

• Check for any possible known issues with Expo Doctor. If you see warnings about duplicate native modules, a guide will appear to help resolve dependency update issues. To temporarily let Expo CLI work around this, enable expo.experiments.autolinkingModuleResolution in app.json. This option is enabled by default in monorepos.

• Refer to the "Deprecations" and "Notable breaking changes" sections above for breaking changes that are most likely to impact your app.
• Make sure to check the changelog for all other breaking changes!
• Upgrade Xcode if needed: Xcode 26 is required to compile a native iOS project. For EAS Build and Workflows, profiles without any specified image will default to Xcode 26.2.
• If you use Continuous Native Generation:
  • Delete the android and ios directories if you generated them for a previous SDK version in your local project directory. They'll be re-generated next time you run a build, either with npx expo run:ios, npx expo prebuild, or with EAS Build.
• If you don't use Continuous Native Generation:
  • Run npx pod-install if you have an ios directory.
  • Apply any relevant changes from the Native project upgrade helper.
  • Optionally, you could consider adopting prebuild for easier upgrades in the future.
• If you use development builds with expo-dev-client: Create a new development build after upgrading.
• If you use Expo Go: consider migrating to development builds. Expo Go is not recommended as a development environment for production apps. Note that Expo Go for SDK 55 is not yet available on stores. You will need to install it through Expo CLI for Android or TestFlight External Beta for iOS. Alternatively, use eas go to create a build of Expo Go for SDK 55 and upload it to your own TestFlight team.
• Having trouble? Refer to the Troubleshooting your SDK upgrade guide.
• Questions? Join our weekly office hours on Wednesdays at 12:00PM Pacific on Discord.

The team, in no particular order: everyone contributed one way or another, with special mentions to the engineers most directly involved in this release: Alan Hughes, Aleksander Mikucki, Cedric van Putten, Christian Falch, Doug Lowder, Evan Bacon, Gabriel Donadel, Kudo Chien, Łukasz Kosmaty, Phil Pluckthun, Vojtech Novak, Wojciech Dróżdż, Jakub Grzywacz, Jakub Tkacz, Tomasz Sapeta, Hassan Khan, Krystof Woldrich, and Nishan Bende. Other contributors include Aman Mittal, Kadi Kraman, Keith Kurak, Quin Jung, Will Schurman, and Stanisław Chmiela. Welcome, Bartłomiej Klocek and Mathieu Acthernoene.

External contributors: Abhishek Raj, Aleksandr Kondrashov, Alfonso Curbelo, Amaury Liet, Andrej Pavlovic, Arthur Blais, Artur Morys - Magiera, Azeem Idrisi, azro352, Bartosz Kaszubowski, benjamin, Benjamin Komen, Benjamin Wallberg, Billy, brianomchugh, Błażej Kustra, C. Obama, CamWass, Choco, Chris Masters, Chris Zubak-Skees, Christian Wooldridge, Dalibor Belic, Daniel Meyer, Daniel Reichhart, Danish, Dave Mkpa-Eke, David Alonso, Delphine Bugner, Dennis Morello, desii, Dimitar Nestorov, Donghoon Nam, Doğukan Yıldız, Dwight Watson, Dylan, Emil Lindén, Eric Kreutzer, Eric Zeiberg, Fernando Rojo, Frank Calise, Gary Chiu, Gregory Moskaliuk, Gustavo Harff, hssdiv, HubertBer, Hugo Extrat, Ian K, Isaiah Hamilton, Jakub Kosmydel, Jc Cloete, Jeroen van Warmerdam, JeroenG, Jesper Sørensen, John HU, Jonathan Baudanza, Jonathan Rivera, Joseph Gift, Julie Saia, jurajpaska8, K.Dileepa Thushan Peiris, Kazuho Maejima, Kfir Fitousi, kimchi-developer, Kornelijus Šliubauskas, Krastan Dimitrov, Kræn Hansen, Kyle Ledbetter, Leonardo E. Dominguez, leonmetthez, Loic CHOLLIER, lucabc2000, Lucia Sarni, Manu, Matin Zadeh Dolatabad, Matthew Abraham, Mauko Quiroga-Alvarado, Maxime, Mikołaj Szydłowski, Mohammad Amin, Momtchil Momtchev, Myagmarsuren, Nicholas Pachulski, Nick Ater, Nicola Corti, Otávio Stasiak, Patrick Michalik, Patrick Wang, Patryk Mleczek, Peter Lazar, Petr Chalupa, Pflaumenbaum, Preet Patel, Randall71, Regi24, roach, Rodrigo Leite Araujo, Ronald Goedeke, Samuel Brucksch, Samuel Newman, Santiago Topolansky, Satyajit Sahoo, Sergiy Dybskiy, Serhii Pustovit, Shane Friedman, Shoghy Martinez, Shridhar Gupta, Shubh Porwal, Shubham Shinde, snowingfox, starsky-nev, teamclouday, Terijaki, TheUntraceable, ThiMal, Tomasz Zawadzki, Ty Rauber, Victor Bolivar De la Cruz, Vsevolod Lomovitsky, xoyseau, yerevin, and Zhovtonizhko Dmitriy.

Beta testers: Agrit Tiwari, Amrit Saini, androidanimation, Anthony Mittaz, Berhan, Brandon Austin, Chris Zubak-Skees, David Grimsley, Dunak, dylanfcsr, Eduardo Lomelí, ifx326, Kenji Okura, Kingfapa, Leonardo E. Dominguez, Lucas Hardt, Matthew Horan, Max, Nikhil Reddy Avuthu, R4Y, Robrecht Meersman, Rodolfo Perottoni, sbkl, Simon, and Sven.