Getting started

Follow these 9 steps to start using Abstract with your team.

Click here to start your 14-day free trial.

1. Join an Organization.

Designers and stakeholders collaborate on Projects inside of Organizations. Your Organization is your team’s home for all design work.

If you’re the first person on your team to join Abstract, you’ll need to create your team’s Organization.

  • Share Libraries
  • Centralize billing management
  • Prevent double-paying for designers who sit on multiple teams / Organizations

2. Download the macOS app.

To edit or create design files in Abstract, you’ll need to download the macOS desktop app. It’s not possible to edit or create design files on Abstract’s web app.

You can view design files, provide feedback, or handle billing payments directly from Abstract’s web app.

3. Decide how to organize your Projects.

In Abstract, you’ll organize your Sketch or Adobe XD files into Projects. Since your team shares Projects, how you divide design files into Projects and name those Projects impacts your entire team.

We recommend organizing your Projects in one of three ways:

  • By platform. This works well for teams that organize their work according to platform, e.g. iOS app, Android app, Web, etc.
  • By feature. This works well for teams that organize their work according to feature, e.g. Onboarding, Activation, Marketing, etc.
  • By client. If you work at an agency, consider organizing Projects by client.

Read our blog or watch our Abstract 101 webinar to learn more about Projects.

4. Create your first Team Project.

Create a Team Project to collaborate with other designers and stakeholders.

5. Add Sketch or Adobe XD files to your Project.

Next, you’ll create the project’s Master—what we call the finalized, approved designs. Your team can discuss and decide which designs are considered “final” for each project. Once aligned, your team can import existing Sketch or Adobe XD files or create new ones.

6. Create a Branch.

Start new work in Abstract by creating a Branch.

Think of a Branch as a working copy of Master that only you can edit. A Branch is where you can explore and edit designs in a Project. You’ll share these designs with your team by committing your changes, as outlined in the next step.

7. Commit your changes.

Each time you arrive at a decision while designing, commit your changes.

A Commit is like a bookmark: you’re marking a point you can return to if needed. If you change your mind about a decision, you can restore a Project’s Master back to any previous Commit and try again. We recommend committing several times a day.

8. Merge a Branch to Master.

Once your Branch is reviewed and approved, you’re ready to merge your changes to Master.

Merging a Branch makes those designs part of Master.

9. Invite team members.

Invite a team member to your Organization to try out the entire Abstract collaboration workflow: Branch, Commit, Review, and Merge.

Advanced setup

These articles may be helpful once you’ve got the basics down: