You can now import any project created in Play 1.0 (our legacy app available from the macOS App Store) into Play 2.0. Once imported, your project will be fully functional and ready for you to continue editing.

To begin importing a project from Play 1.0, click the “Import 1.0 Projects” button in the Projects tab. Select the project you would like to import from the drop down list that appears. You need to import each project individually based on the name, so we recommend going back into Play 1.0 to familiarize yourself with your existing projects.

A pop-up will appear letting you know that this process will duplicate a version of the project into Play 2.0 while also keeping a version in Play 1.0. Pressing “Duplicate and Open” will start the import process.

Once the import is complete, you can open your project!

You can import 1.0 drafts the same way from the Drafts tab.

Please note: the import button will only be available if you have projects from Play 1.0 in the team you are currently on

All interactions created in Play 1.0 will still work in projects imported into Play 2.0. You can edit these interactions and create new ones within the project, but there are some important factors to consider.

Since we improved Interaction Mode in Play 2.0, many 1.0 interaction nodes (triggers and actions) are different from their 2.0 counterparts. Often there are new trigger or action properties. For example, 1.0 Tap trigger don’t have any properties, but 2.0 Tap triggers have two properties: Number of Taps and Number of Fingers.

To keep things simple, all of your existing interactions nodes will come over as 1.0 interaction nodes, indicated by an orange warning icon. Any new interactions created in the project will use 2.0 interaction nodes.

Projects can have a mix of 1.0 and 2.0 interactions, but we do not recommend mixing 1.0 and 2.0 nodes within individual interactions. If you want to add to a 1.0 interaction with a new action or condition, we recommend recreating the interaction using 2.0 nodes. If you have questions on how to do this, feel free to reach out to our support team!

Other 1.0 nodes don't exist at all in Play 2.0. Typically, this is because they were custom instead of native. In these cases, we've created and substituted nodes in Play 2.0 that accomplish the same thing.

For example, Toggle Tap is not a trigger that exists in SwiftUI, but it was a popular trigger in Play 1.0. Any imported Toggle Tap triggers are replaced with a Toggle Tap prefab that lets you add "First Tap" actions and "Second Tap" actions. Under the prefab's hood, you'll find a Tap trigger with conditional logic, if you're curious.

If you have any issues, please reach out to [email protected].