How large teams use RocketSim

Making the most of RocketSim’s features when collaborating in larger teams.

Many large teams make use of RocketSim to improve their development workflow. Developers, but also QA engineers and designers make use of RocketSim to validate designs, accessibility implementations, or execute deeplinks to enable certain feature flags.

This article provides an overview of features that work best for specific cases, allowing you to explore what RocketSim has to offer.

Sharing App Actions using Git

RocketSim allows you to save app actions per bundle identifier. App actions include deeplinks, push notifications, and locations that you commonly use to build and test your app.

By storing your configuration in Git, you allow all your team members to benefit from the same set of app actions related to your bundle identifier.

Notion image

Enabling feature flags

Many teams develop new features behind so-called feature flags. It’s common to have an in-app debug view that shows up after a hidden gesture like shaking the device.

RocketSim introduces an alternative to these debug views by allowing you to switch flags using the realtime User Defaults Editor.

Notion image

Preparing for European Accessibility Act (2025)

Your team should prepare for the European Accessibility Act and RocketSim is here to help. The environment toggles allow you to validate all kinds of accessibility related implementations, including dark mode and dynamic type.

Notion image

How designers and QA engineers validate implementations on the Simulator

Besides developers, it’s also QA engineers and designers that benefit from RocketSim. Large teams deliver Simulator builds automatically via CI, attached to every PR. Both designers and QA engineers will run the build on the Simulator and use RocketSim to validate.

  • The design comparison feature ensures pixel-perfect views.
  • Recordings with touches help QA engineers to better explain bugs.
  • Relaunch apps in specific locale or timezone without resetting the Simulator greatly improves the QA testing cycle.
  • Accessibility toggles in RocketSim’s side window takes away the need to teach your testers how they can switch common accessibility modes.

The future of RocketSim

RocketSim’s goal is to make you build apps faster. Allowing teams to work more efficiently with RocketSim will automatically speed you up, which is why this is a focus for 2024 development.

Based on my personal experience in large teams, as well as conversations with teams that currently use RocketSim, I’m working on a set of improvements tailored for more efficiency within teams of multiple iOS engineers.

If you’re considering RocketSim for your team, make sure to get in touch with for a personal introduction on how RocketSim can help your team develop faster.

Did this answer your question?