And I still get lost trying to find animation prototypes, durations, timing functions, etc
Figma makes 200 fixes and improvements to Dev Mode
51–60 of 70 posts
Re: Figma makes 200 fixes and improvements to Dev Mode
#52Broadly this is great to see and I’m sure the team has worked hard on this. But can’t help but feel like this is a bit of knee jerk reaction to the growth of the much smaller open source product Penpot, that’s received increasing interest and even some funding since the Figma sale was announced. Penpot has bet on making all the controls match the html/css spec as well as save everything as svg, in short having a big…
That's not been my impression as a designer. Outside of HN, I've not seen anybody talk about switching to Penpot. My team even looked at it and concluded it was several evolutionary steps from being an option. It's not a viable replacement for Figma yet. To be clear, I'd love it if it were, because I want competition in a space Adobe is trying to monopolize, I just don't feel like Penpot is providing that pressure at…
To paraphrase Reed Hastings' classic line: Penpot needs to become Figma before Figma can become Penpot.
Re: Figma makes 200 fixes and improvements to Dev Mode
#53Earlier quoted context omitted.
$25/mth seems like an egregious price for such an unhelpful feature. I understand it will get better, but at this point... I can't imagine paying more than $5/mth on top of my current price assuming it was more polished. Maybe I'm not the target market. I can transcribe visuals to CSS and HTML fairly automatically due to so many years of doing it, and I can do it reliably and consistently in ways that fit various wor…
Dev Mode is included in the $15 per editor Professional tier. $25 Dev Mode stand-alone subscription is a less expensive option for Organization or Enterprise tiers, which are $45-75 per editor.
Re: Figma makes 200 fixes and improvements to Dev Mode
#54Earlier quoted context omitted.
Are the teams working on Figma known to be like that? I’ve only heard good things about Figma honestly, but all before the purchase by Adobe.
PM over here at Figma. We don't have dedicated bug teams whose only job is to fix incoming bugs. Feature teams are responsible for their own bugs, so we typically have an ebb and flow of feature work vs quality work. Quality is also pretty high on our pri list for leadership, so we typically don't have pushback if we want to focus on bug fixing vs pursuing new features. Also just FYI, the purchase hasn't gone through…
Re: Figma makes 200 fixes and improvements to Dev Mode
#55Broadly this is great to see and I’m sure the team has worked hard on this. But can’t help but feel like this is a bit of knee jerk reaction to the growth of the much smaller open source product Penpot, that’s received increasing interest and even some funding since the Figma sale was announced. Penpot has bet on making all the controls match the html/css spec as well as save everything as svg, in short having a big…
Posting anonymously as I have made some investments in the design tooling space. Overall I don't see Penpot being a realistic competitor to Figma, and I can't see this as being something that was done as a knee jerk reaction to Penpot's social success. First, why it isn't a realistic competitor. While building everything out leveraging SVG as its main rendering engine allows for parity with code as an advantage, the…
It is not mutually exclusive that Figma bought Visly in 2021 and these features are in reaction to/are copying Penpot. Given the gap of three years between this post while owning Visly makes it more plausible.
Re: Figma makes 200 fixes and improvements to Dev Mode
#56Re: Figma makes 200 fixes and improvements to Dev Mode
#57Figma has been such a cool story, I'm so disappointed that the buyout wasn't blocked. Obviously it's an awesome tool and still getting better, but competition is a good thing and I'd really hoped in 5 years we'd have figma and others pushing adobe to be more innovative and user-friendly.
Re: Figma makes 200 fixes and improvements to Dev Mode
#58Broadly this is great to see and I’m sure the team has worked hard on this. But can’t help but feel like this is a bit of knee jerk reaction to the growth of the much smaller open source product Penpot, that’s received increasing interest and even some funding since the Figma sale was announced. Penpot has bet on making all the controls match the html/css spec as well as save everything as svg, in short having a big…
Posting anonymously as I have made some investments in the design tooling space. Overall I don't see Penpot being a realistic competitor to Figma, and I can't see this as being something that was done as a knee jerk reaction to Penpot's social success. First, why it isn't a realistic competitor. While building everything out leveraging SVG as its main rendering engine allows for parity with code as an advantage, the…
Regarding the "isn't a realistic competitor" point. You bet we are! The only realistic competitor in a while, actually, because we come from a deep understanding of how cross-functional teams address design & code instead of doubling down on silos or "modes". To be successful you need to do things VERY differently.
- We're open source and we're enjoying an extremely active community of contributors.
- We rely on open standards so designers (and organisations) can own their future while developers can treat design files as first class citizens in a git repo if they want to.
- You can use SaaS or self-host, we don't care about your deployment strategy.
- We bring code vocabulary and abstractions to the design process (see Flex Layout or upcoming Grid Layout https://www.youtube.com/watch?v=kx0ufKErqVk) so we get rid of the lost in translation issues that plague teams.
- We partner with people like Design Tokens (which are also open source) to build the future of Design Decisions so we can transcend the current status quo of design systems.
Yes, of course we have performance challenges with SVG on browsers (not Figma 2MB WASM memory limits, though, since we can access DOM memory availability which is now 16GB!) but these are temporary engineering challenges and we're working super hard on cracking them.
I'm fine having these debates on whether Penpot is a viable competitor to Figma, it's healthy and I get it, it happens all the time when new tools pop up (sometimes signalling the end of a cycle, even if it's not sudden). But what really matters to us at Penpot is that this goes beyond "competing" with a particular tool, this is about a specific world vision on how designers and developers want to collaborate to scale up design and software building.
And a key ingredient to all this is "what are developers going to do?" That's the real battleground out there. Developers outnumber Designers 10 to 1. People that keep wondering why Adobe paid $20B for Figma tend to miss the point. It's the developers, obviously! Of course they are worth $20B when you're not exciting to them!
This is not a static picture, it never was and it never is. Every single day we keep working hard on building the best design & prototyping tool for designers and developers, every single day we're re-balancing the status quo. It's already paying off with 400K+ users worldwide, half of them on self-host.
To be honest, we can't be more excited about everything that's going on and what's making everything worth it's not just the growing community of users and contributors but the amazing quality of it, these are not casual users coming for the free stuff, these are forward thinkers really getting it!
Re: Figma makes 200 fixes and improvements to Dev Mode
#59I use Figma to design and then build what I design. This might be a bit unusual :) The switch to "Dev Mode" as a different modality has unfortunately been a bit frustrating, because I can no longer hop back and forth between designing and grabbing "developer" values (e.g. Android ARGB colour values). This means I'm toggling in and out of dev mode for only a few seconds. I wish the Figma team had found a way to introd…
Re: Figma makes 200 fixes and improvements to Dev Mode
#60I can guess what's coming next: dev mode will get locked behind the "editor" per user pricing and then it's going to become a pain getting stuff out of Figma. Also, there's an annoying "bug" in Figma when it tries to implement its own hotkeys: I have various Ctrl/Cmnd key combos swapped and hitting Ctrl causes Figma to de-select whatever I've highlighted so that trying to copy some portion of a colour code or whateve…
> In 2024, Dev Mode will be included in all editor seats or can be purchased separately for $25 per seat/month on Organization, and $35 per seat/month on Enterprise. https://www.figma.com/pricing/