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.

Show previous messages

November 3, 2017 at 1:17am

Rey Alejandro@rey-alejandro

1:17am

I agree, I'd love to see a roadmap

November 3, 2017 at 12:38pm

Sorcha Moore@sorcha-moore

12:38pm

November 8, 2017 at 8:56am

Gunnar Lockwood@gunnar

8:56am

I imagine a roadmap would be very tricky to share from a business perspective. Nested components would be great, you're right!

November 8, 2017 at 4:49pm

Glen Lipka@glenlipka

4:49pm

+1 Roadmap - At least for 3 months ahead.

December 11, 2017 at 5:02am

Gav@rollyjoger

5:02am

I'm already using Figma and love it but would love to see a roadmap!

Bryn Jackson@bryn

8:39am

If you think about the fact that you’re asking a company to make their plans available to some customers but also their many competitors... it would be unwise for them to accommodate this request.

Andrey Grabelnikov@grabelnikov

2:13pm

Would love to see it

Ivan Paudice@ivan-paudice

2:17pm

plus one here-

December 11, 2017 at 9:43pm

Glen Lipka@glenlipka

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

Lubos Kmetko@lubos-kmetko

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

The Big Picture@the-big-picture

5:30pm

Would love a roadmap as well. Although, surprise updates feel a bit like Christmas when they happen. :)

December 20, 2017 at 2:50pm

Ali Khomami@ali-khomami

2:50pm

🆙

Marco Rodrigues@marco-rodrigues

6:05pm

With all the great stuff they added this year. I might be making the switch. I love when companies have insight into whats to come. +1 for a Roadmap

February 2, 2018 at 2:20am

Ray Zaranza@rayzaranza

2:20am

Denis Rojčyk@rojcyk

7:08am

Johanna Stuke@johanna

12:15pm

+1, would help me argument for a switch to Figma in the team.

February 3, 2018 at 11:07am

Eugene Belyaev@eugene-belyaev

11:07am

February 6, 2018 at 9:19am

Maksim Mukhachev@inteo

9:19am

February 9, 2018 at 12:10pm

Pixel Lens@pixel-lens

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

Ryan Payne@ryan-payne

4:49pm

+20

February 14, 2018 at 1:57am

Lucas Santos@lucas-santos

1:57am

February 14, 2018 at 8:10am

Ian Steven Mancera@mancerrss

8:10am

+100

November 1, 2018 at 6:41pm

Marc Deely@marcusdeely

6:41pm

Absolutely. With so many design+prototyping softwares out there, it's frustrating that no two services offer the same useful features. Knowing a roadmap and what you are prioritizing will at least help me decide if you're in the direction that I need you to go in.

December 27, 2018 at 10:48am

Alexander Vinogradov@revenga

10:48am

Brandon Oxendine@brandonhaslegs

11:06am

Anyone have more examples of public roadmaps?

Show more messages