Figma roadmapNovember 2, 2017 at 11:30am (Edited 2 years ago)
Here, at Kapsch, we are planning the design of a very large application dedicated to Traffic and Transport.
Releases page (http://releases.figma.com) is fine but a roadmap is needed in order to make a full switch from Sketch.
It would be very helpful to know when you are going to address updates such as being able to use components in different files without breaking the links or when we will be able to use nested components in the Team library.
This last one is important because we work from several countries at the same time.
Thanks in advance.
November 8, 2017 at 4:49pm
December 11, 2017 at 5:02am
December 11, 2017 at 9:43pm
@byrn I have been working on startups for 25 years. I have never seen a company fail due to their 3 month roadmap being visible to the public. You can fail for lots of reasons, this one is more about paranoia than real consequence.
December 14, 2017 at 8:24am
I don't think making a public roadmap could do any harm to the business. In fact, it could help them to win new customers. Avocode has a nice roadmap - https://avocode.com/product-roadmap - where btw. I've learned they plan to support Figma in the future ;)
December 19, 2017 at 5:30pm
December 20, 2017 at 2:50pm
February 2, 2018 at 2:20am
February 3, 2018 at 11:07am
February 6, 2018 at 9:19am
February 9, 2018 at 12:10pm
This is definately a great idea since Figma is still a pretty raw tool at the moment. It has some stuff made well, but even more stuff it lacks. This wouldn't be an issue if Figma wouldn't position itself as all-in-one prototype, UI-design, UX-design, and design-system tool. People need to know whether they should stick to Figma or just stay with oldschool trusted workflows, despite their flaws, since all flaws are well-known and workarounds are also found-out.
February 13, 2018 at 4:49pm
February 14, 2018 at 1:57am
February 14, 2018 at 8:10am
November 1, 2018 at 6:41pm
December 27, 2018 at 10:48am
Actually, all mentioned features (component in different files, nested components in the team library) are already working so... what is the problem here? There will be more new features from Sketch and new features from Figma - who knows what the future will bring but I'd say Figma has a tactical advatage :)
February 6, 2019 at 9:42pm
The roadmap is necessary! For example, I have a project shared on InVision. I want to switch to Figma, but Figma doesn't support export to InVision (don't tell me about PNGs). Figma doesn't support plug-ins, so there's no way InVision will move in this direction. I need to know if Figma plans to support InVision in general, to make my decisions.
While we don't have a public roadmap we do try and be honest and open with our users about what we're focusing on. @okyr we don't currently have any plans to build out an Invision integration, and it's pretty unlikely that we will. As far as plug-ins go this is something we're working toward so stay tuned on this. :)