Where the design community meets.
Florida, United States Director of UX / UI Joined over 4 years ago
A good designer is more than simply age. It's general wisdom, and patience. The ability to communicate, and more importantly listen. As the author says these traits are present at any age, but in general come with time. I'd include an additional point, that with the world's demographic is shifting to 40+ years of age (really older), it's more important than ever to really put a concerted effort into understanding, and catering to the older generations. I've known quite a few agencies that have hired designers over 50 to achieve that perspective. The world isn't young, but varied. Companies should start realizing this, or risk losing grasp of their world presence.
Try using Figma to build a component for a button with horizontally centered icon & text inside of it. This shouldn't be an issue in 2019, but here we are.
I do think stacks are great. But I can do that fairly easily in Figma with grids and constraints.
That sounds amazing, and I would love to do the same, but unfortunately, that seems like a luxury only afforded to big companies with virtually unlimited resources. I'm having a hard time imagining smaller companies being able to dedicate the necessary engineer and designer resources required for building this out.
Very true. That’s the nice thing about Figma. It’s much more incremental. I’ve started with color, and text being defined by Figma. And the advantage with Figma is that you aren’t locked into any single ecosystem that could go the path of jQuery. And designers don’t all have to no how to work with code to modify parts of the system.
Read data in Sketch
This has always been possible with plugins.
Stacks in Framer X
Still don't see this as that much of a benefit, and you are locked into a technical approach of designing instead of freeform. I don't really understand the love of Stacks. Sketch had similar functionality in plugin form, and the larger benefit of the feature is similar to dynamic grids.
Figma did release exclusive features recently (e.g. API, dynamic grids,...) but ultimately those didn't materialize in significant benefits in daily use
I can tell you that a number of organizations are using the Figma API to build rapid prototyping with React. Saw some great demos at a conference.
Michael: I think you are missing the $45/editor located above the contact sales button. Though when sales spoke with me they gave me a much larger number.
Yeah. The components losing values when updated is a big annoyance. I've reported that a few times.
I really wish Enterprise offered more value. It's really just group pricing, and the ability to create teams. Fonts, and organization library is....well not really much. Organization libraries are great, but with a single team you get pretty much the same workflow. Fonts can be useful for remote teams, and collaborating with contractors. But really it's not significant enough to warrant the cost just for that. It's pretty simple to just share an asset folder (which we do already for other assets). Activity seemed to be a rough afterthought with little polish, and is missing a lot of functionality I'd like to see, and needs to be much more forward facing. Figma needs some sort of true Dashboard view at the Enterprise level.
I scheduled a demo to see if it was useful for our organization. The sales contact didn't really demo it effectively. The individual that demoed Enterprise services didn't properly introduce themselves, and seemed confused about their role in Figma. I came up with some possible solutions for my own questions after the meeting, since the sales individual didn't really seem to know the tool enough to come up with workarounds. I also found it odd that they were doing the demo while at the beach. Lots of static, and audio clicked in and out. Cool, and hip to be at the beach for sure, but come on! I'm at a coffee shop myself right now, but for conference calls (beyond standups) I'll move somewhere quiet.
My main wish with Enterprise was to allow more fine grained control over permissions, and UI visibility. Detailed into the following roles:
It would also be very useful to be able to only share specific pages, frames, etc. and not display anything else. This is easy enough to workaround by exporting, or having a separate file. BUT this defeats much of the benefit of Figma where comments can reside in the core project file, and not separated out in other files.
I really hoped versioning would also have more functionality within Enterprise. In general this needs to be more focused, and fleshed out. Being able to branch files into duplicates, but retain the connection to the previous file (in the sense of this is from X). Would really make versioning better. Really I have many wants to versioning that is missing.
Part of the whole reviewing of files. Having something simple where frames, and pages have a CTA when changes have occurred since your last visit would be a game changer when dealing with stakeholders, and business sponsors. I can again work around that by doing it manually. (which I do) But having that group into versioning would be nice.
The help documentation is decades old online. I've been working on my own cookbook / manual that I use to onboard contractors, and as a reference because I can't really direct them to help. Most of the screenshots are outdated, and don't show the current interface. Documentation on many of the features is very primitive, and doesn't really explain the HOW something works. This isn't directly related to Enterprise, but I feel is worth mentioning for anyone that comes across this mini-review. I've discussed this with a few internal members of Figma, and I know they are aware of the issues and are working on it.
All of this said. I love Figma. I'm an evangelist, and run the Tampa Bay Meetup. I'm always sharing, and talking about it. I've personally converted dozens of individuals to paying Figma users. But I'm continually frustrated by the slow pace of management level capabilities. I imagine time will eventually lead to solutions to some of my concerns. Use Figma!
Great article as always. I'm going to have to explore some SVG Filters now.
If you are interested in the HP Envy 34 AIO I'd suggest you consider the Surface Studio 2 too. The Studio gets you a much better screen, and design. The keyboard and mouse for the HP are garbage compared to what Microsoft provides. Plus the Studio will get you pen input that is significantly more useful than you might think. Do NOT get the original Studio. It runs a Fusion style drive that is very slow. The only negative with the Studio 2 is no TB3 USB-C ports.
The grass isn't greener on the other side, and you will run into annoyances on a Windows devices. If you are deep in the Apple ecosystem I'd suggest trying to solve the problems (as it looks like you are doing.)
I have a Surface Book 1.5 (which has a decent GPU performance base), and it's excellent hardware. I really enjoy it, but it isn't all roses. I go back and forth between it and my MacBook Pro.
I understand. You want to freshen up your workspace. I’m a big fan of Microsoft’s newer ergonomic keyboards.
It's about a new identity for a product used by over a billion people.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.