Philosophy Behind Muta

Michael Foster

We designed Muta to be as simple and straightforward as possible, while still solving the main bottlenecks to building optimized mobile app onboarding flows.

With simplicity in mind, Muta is made up of three core elements: Flows, Templates, and Placements.

Flows

Flows are Muta's bread and butter. Flows contain the actual screens that make up the user journey. Screens contain a variety of core elements including:

Shapes
Icons
Images
Text
Buttons
Progress Bars
Loading Spinners
Text Inputs
Multiple Choice Questions

You can have as few or as many screens as you want in a Muta Flow. Screens can be rearranged, added, deleted, and duplicated. Completed Flows can be previewed on our in-app simulator. This allows the developer to get an instant feel for what users will experience when walking through the Flow.

Templates

What if you’re not sure where to start with a Flow? This is why we built Templates. Templates are premade Flows that follow playbooks we’ve seen work best for the top performing apps. First, find a template you like. Then, use this template as a baseplate and adjust it to fit your goals. We are adding more templates every day. Want to see a specific onboarding turned into a template? Send me a link—I'm happy to make it happen!

Placements

Placements are a container for Flows. The goal of Muta is to help limit your code changes to only the core product. Create a Placement, give it an ID, and select a Flow to live in that Placement. In your app code, pass the Placement ID to a function called displayPlacement(). Whenever that function is called with the Placement ID, the Flow living inside of it will be displayed on the screen. The beauty behind this is that Flows are swappable. That means that if your app displays Placement 1, and Placement 1 displays Flow A, all you have to do to display Flow B is swap it with A in our web app. This concept allows you to completely change your onboarding Flow with no code change and no App Review. Of course, you can also edit any existing Flow while in a Placement. Once you hit publish, the next user that downloads the app will see the latest Flow.

Make sense?

You should now have a good mental map of how Muta works. If you have any questions, comments, feature requests, or good stories, feel free to live chat with me in the bottom right or even schedule some camera time at the link below. I look forward to hearing from you!

https://calendar.app.google/HvbY1R9P4eGiiaXZ9

Best,

Michael