Alternatives to Avocode logo

Alternatives to Avocode

Zeplin, InVision, Abstract, Figma, and Marvel are the most popular alternatives and competitors to Avocode.
48
59
+ 1
48

What is Avocode and what are its top alternatives?

Avocode is a cross-platform app that helps designers and developers collaborate and easily handoff designs. Avocode comes with 14 days free trial.
Avocode is a tool in the Interactive Mockups category of a tech stack.

Top Alternatives of Avocode

Avocode alternatives & related posts

Zeplin logo

Zeplin

610
326
12
610
326
+ 1
12
Collaboration app for UI designers and frontend developers
Zeplin logo
Zeplin
VS
Avocode logo
Avocode

related Zeplin posts

Adam Neary
Adam Neary
Engineer at Airbnb · | 9 upvotes · 605K views
atAirbnbAirbnb
React Storybook
React Storybook
Zeplin
Zeplin
Figma
Figma
Apollo
Apollo
#ReactDesignStack
#StorybookStack
#StorybookDesignStack

The tool we use for editing UI is React Storybook. It is the perfect place to make sure your work aligns with designs to the pixel across breakpoints. You get fast hot module reloading and a couple checkboxes to enable/disable browser features like Flexbox.

The only tricks I apply to Storybook are loading the stories with the mock data we’ve extracted from the API. If your mock data really covers all the various various possible states for your UI, you are good to go. Beyond that, if you have alternative states you want to account for, perhaps loading or error states, you can add them in manually.

This is the crux of the matter for Storybook. This file is entirely generated from Yeoman (discussed below), and it delivers the examples from the Alps Journey by default. getSectionsFromJourney() just filters the sections.

One other hack you’ll notice is that I added a pair of divs to bookend my component vertically, since Storybook renders with whitespace around the component. That is fine for buttons or UI with borders, but it’s hard to tell precisely where your component starts and ends, so I hacked them in there.

Since we are talking about how all these fabulous tools work so well together to help you be productive, can I just say what a delight it is to work on UI with Zeplin or Figma side by side with Storybook. Digging into UI in this abstract way takes all the chaos of this madcap world away one breakpoint at a time, and in that quiet realm, you are good down to the pixel every time.

To supply Storybook and our unit tests with realistic mock data, we want to extract the mock data directly from our Shared Development Environment. As with codegen, even a small change in a query fragment should also trigger many small changes in mock data. And here, similarly, the hard part is tackled entirely by Apollo CLI, and you can stitch it together with your own code in no time.

Coming back to Zeplin and Figma briefly, they're both built to allow engineers to extract content directly to facilitate product development.

Extracting the copy for an entire paragraph is as simple as selecting the content in Zeplin and clicking the “copy” icon in the Content section of the sidebar. In the case of Zeplin, images can be extracted by selecting and clicking the “download” icon in the Assets section of the sidebar.

ReactDesignStack #StorybookStack #StorybookDesignStack
See more

related InVision posts

Priit Kaasik
Priit Kaasik
Engineering Lead at Katana MRP · | 8 upvotes · 280.3K views
atKatana MRPKatana MRP
Confluence
Confluence
Bitbucket
Bitbucket
GitHub
GitHub
Jira
Jira
Microsoft Office 365
Microsoft Office 365
Slack
Slack
InVision
InVision
Sketch
Sketch

How we ended up choosing Confluence as our internal web / wiki / documentation platform at Katana.

It happened because we chose Bitbucket over GitHub . We had Katana's first hackaton to assemble and test product engineering platform. It turned out that at that time you could have Bitbucket's private repositories and a team of five people for free - Done!

This decision led us to using Bitbucket pipelines for CI, Jira for Kanban, and finally, Confluence. We also use Microsoft Office 365 and started with using OneNote, but SharePoint is still a nightmare product to use to collaborate, so OneNote had to go.

Now, when thinking of the key value of Confluence to Katana then it is Product Requirements Management. We use Page Properties macros, integrations (with Slack , InVision, Sketch etc.) to manage Product Roadmap, flash out Epic and User Stories.

We ended up with using Confluence because it is the best fit for our current engineering ecosystem.

See more
Abstract logo

Abstract

77
48
3
77
48
+ 1
3
A platform for modern design teams to work together
Abstract logo
Abstract
VS
Avocode logo
Avocode

related Figma posts

Adam Neary
Adam Neary
Engineer at Airbnb · | 9 upvotes · 605K views
atAirbnbAirbnb
React Storybook
React Storybook
Zeplin
Zeplin
Figma
Figma
Apollo
Apollo
#ReactDesignStack
#StorybookStack
#StorybookDesignStack

The tool we use for editing UI is React Storybook. It is the perfect place to make sure your work aligns with designs to the pixel across breakpoints. You get fast hot module reloading and a couple checkboxes to enable/disable browser features like Flexbox.

The only tricks I apply to Storybook are loading the stories with the mock data we’ve extracted from the API. If your mock data really covers all the various various possible states for your UI, you are good to go. Beyond that, if you have alternative states you want to account for, perhaps loading or error states, you can add them in manually.

This is the crux of the matter for Storybook. This file is entirely generated from Yeoman (discussed below), and it delivers the examples from the Alps Journey by default. getSectionsFromJourney() just filters the sections.

One other hack you’ll notice is that I added a pair of divs to bookend my component vertically, since Storybook renders with whitespace around the component. That is fine for buttons or UI with borders, but it’s hard to tell precisely where your component starts and ends, so I hacked them in there.

Since we are talking about how all these fabulous tools work so well together to help you be productive, can I just say what a delight it is to work on UI with Zeplin or Figma side by side with Storybook. Digging into UI in this abstract way takes all the chaos of this madcap world away one breakpoint at a time, and in that quiet realm, you are good down to the pixel every time.

To supply Storybook and our unit tests with realistic mock data, we want to extract the mock data directly from our Shared Development Environment. As with codegen, even a small change in a query fragment should also trigger many small changes in mock data. And here, similarly, the hard part is tackled entirely by Apollo CLI, and you can stitch it together with your own code in no time.

Coming back to Zeplin and Figma briefly, they're both built to allow engineers to extract content directly to facilitate product development.

Extracting the copy for an entire paragraph is as simple as selecting the content in Zeplin and clicking the “copy” icon in the Content section of the sidebar. In the case of Zeplin, images can be extracted by selecting and clicking the “download” icon in the Assets section of the sidebar.

ReactDesignStack #StorybookStack #StorybookDesignStack
See more
Marvel logo

Marvel

154
115
45
154
115
+ 1
45
Prototyping for everyone
Marvel logo
Marvel
VS
Avocode logo
Avocode
Axure  logo

Axure

56
24
0
56
24
+ 1
0
Create interactive clickable prototypes for Web, Desktop or Mobile applications
    Be the first to leave a pro
    Axure  logo
    Axure
    VS
    Avocode logo
    Avocode
    Proto.io logo

    Proto.io

    31
    38
    9
    31
    38
    + 1
    9
    Build high-fidelity fully interactive mobile app prototypes in minutes
    Proto.io logo
    Proto.io
    VS
    Avocode logo
    Avocode
    Moqups logo

    Moqups

    14
    11
    0
    14
    11
    + 1
    0
    Online mockups and wireframes made easy
      Be the first to leave a pro
      Moqups logo
      Moqups
      VS
      Avocode logo
      Avocode