#Avocode design soft how to#

For each issue, we have asked the respondent to evaluate how critical this issue is. Therefore we have asked our customers, our Slack Community and also the whole team at Avocode about what could be done better in the product UX. While we have multiple product oriented people in-house, to keep challenging the way our product works, we need to invite more people to the table.

This way every opinion is heard and considered and helps us define the development brief for our product team. It allows us to add context and customer qualitative feedback to particular features. Not having these two things together made it difficult to regularly check the input from our users.Īfter trying a few solutions we ended up with productboard. And as you can imagine, managing so many inputs and deciding which goes first can get messy and demands a lot of time.įirst, we needed to merge the place where we collect feature suggestions with the place where we prioritize our roadmap. These things are hard to plan for, however, they need to be done, because their impact is significant.Īs you can see, the feature roadmap is always a compromise between these three inputs: community, our product team, and the market shifts.

When the market moves - for example when a company like Adobe offers us a partnership to integrate with Adobe XD - we need to be agile to make it happen.

So whenever we receive a new ticket with a feature request we need to balance the importance of such feature against the performance of our underlying technology that needs to work seamlessly, otherwise, any other feature wouldn’t be relevant. That’s why we have dedicated a reasonable amount of time to build a custom rendering engine. We believe that focusing on technology first pays off in the long run. Having built Avocode to solve design hand-off for our team just as for the community, we have a pretty clear idea what Avocode should be able to do. Our product codebase is quite robust, so we have to plan before we edit its parts.Also, we would get a ton of feedback from our customer support channels (Intercom, Twitter, Facebook, Slack Community…). Our community (users, leads, fans) were able to report bugs on GitHub or suggest and upvote feature requests on UserVoice.Until recently, this is how our workflow looked like: we value results over working extra hours,.In fact, one of our five company values is to: Work smarter, not harder. However, we’re always open to challenging our workflow and tool stack to streamline our work.

#Avocode design soft how to#

These symbols (“-“ or “_”) are our syntax marks for skipping artboards and Pages in case you do not want to sync them with your file, therefore if all artboards or Pages are prefixed with it, the upload fails.Today, we’d like to give you a brief look behind the scenes of how we plan our product features.Īfter many years in the digital product development business, we have come up with many workflows how to track feature requests and how to plan their development. Second thing that might cause this issue is when all your artboards or Pages are prefixed with “-“ or “_” in the artboard or Page name. We cannot display layers which are not inside of any artboard at the moment, so if we can't find at least one artboard in the design, the upload fails. The reason may vary, but usually, it is some form of a pattern formed from a lot of vector layers (stripes, world map made of vector dots.).You can combine all the path layers which form that shape to be exported as one layer with Layer -> Combine -> Union - this will create a single layer out of them that should export correctly and much faster.įirst of all make sure that the Sketch file actually contains at least one artboard. That might happen when there are too many layers in the design. We are in contact with the Sketch team and working on its implementation. At the moment, we do not support Sketch 58 smart layout feature. We need to collect more user feedback to decide which way is better.Ģ. We know how to expand the bounds to make the whole text layer visible, but this would change the text layer bound, i.e., they would differ from Sketch. When you create a text layer like this in Sketch at first the whole text line is visible (even what overlaps outside the text layer bounds), but when you edit it for the second time the overlapping parts of the text layer are cut away.

This is caused, because Sketch allows such behavior: You can fix this simply by going to Sketch and enlarging the text field so the whole text stays inside the layer bounds. If the layer bounds of a text layer are smaller than the whole area of text characters in the area, the text layer in Avocode will be cut away.