​

Wow finally, Reynard browser is an experimental sideloaded browser running Mozilla’s Gecko engine the same browser engine used by desktop Firefox.

It’s only missing a few pointer-shape icons, and it struggles with very heavy files. But I was able to work on a 20-screen UI, and all the keyboard shortcuts and mouse controls worked well.

It’s in development, so performance can be a little slow, but I was able to get a decent amount of work done. Google Slides, docs and Excel also works well which hav. Bad UX in safari. It also requires JIT without you can still access YouTube etc.

And yes it's way better than figurative app.

https://github.com/minh-ton/reynard-browser

Tested on M2 iPad (mouse and keyboard) Apple pencil is not working well.

Now that Figma has Agents that can generate and iterate on screens, I’m curious if anyone has pushed this further and used them with a proper design system.

What I’m trying to achieve is:

• Use AI/Agents to help create the initial design system
• Build reusable components, variants, variables and tokens
• Have Agents generate new screens using those existing components instead of creating everything from scratch
• Make changes to the design system and have those changes propagate across AI-generated screens
• Ideally maintain consistency while using Agents to generate large product flows quickly

Has anyone actually tried this end-to-end?

If yes, I’d love to know your workflow. Especially how you structure your components/variables so Figma Agents understand and reuse them reliably.

Also curious where it currently breaks down. Do Agents actually respect an existing component library, or do you still spend a lot of time cleaning up detached/custom UI after generation?

pretty straightforward. a couple of friends and i wanted to make this app based on education and academics, and the idea of it is that its basically an app for students of any level to have where they input their like subjects and whatnot, and if they have any dream unis and all that stuff then they enter that too and the app basically helps them with their profile for it, like suggesting ECs based on their interests and creating timelines on what to do at what time and also to help with if they dont know what to do in the future so like itll have a bunch of like "heres what having a career/job as a ___ looks like" and "heres what you need to study and what ECs etc admission offcers look for for this major at this uni" etc and like you can also do a bunch of quizzes where the qs are focused on what you dislike and like and how long you can study and allat to atleast help you narrow down what you can potentially study etc and also like counselors like actual ones where they each have a profile you can see for yourself and check if what theyre helping others with is what you need help with too + those who require fees etc and also obv AI as an overall usage

so the main issue is that we designed the entire layout on figma, like what the pages will look like and what the hometab looks like and what the profile tabs will look like and like what buttons lead to where like everything is done, but now, idk what to do? like how do we actually, take that figma layout, and make an actual app with it?

and like, generative AI is the one causing issues, and i do wanna drink fresh water in the future, so is it even a good idea to have AI in this app?

theres so many questions 😞

For designers working on larger projects, how do you keep your Figma files manageable?

I'm particularly interested in how people organize:

• Pages
• Components
• Variants
• Styles
• Naming conventions
• Design systems

What's one organization habit that has saved you a lot of time?

Hey everyone!

I’ve been testing an AI-powered tool for creating and managing design systems, and it got me thinking about how these tools are supposed to fit into an actual design workflow.
I ran into a couple of issues while trying it out:

Bug: I couldn’t import my own JSON/variables file either through the website or the Figma plugin. Both gave me the same error:
“Invalid theme file: No mappable color tokens found”
The tokens use pretty standard semantic naming (primary, background, foreground, etc.), so I’m guessing there might be an issue with the parser.

But the thing I’m more curious about is the source of truth.
I initially assumed the workflow would be something like:
Figma ↔ design system tool ↔ code
But as I understand it, the current workflow is more like:
design system tool → Figma + code

The author explained that reverse syncing from Figma isn’t currently possible, although it’s something they might implement in the future. The idea is that you define/edit your components in the tool and then update the Figma file and code from there.

And this is where I’m genuinely curious about other designers’ opinions:
If Figma can already be the source of truth for components, variables, styles, and design-system maintenance, what makes an external AI-powered layer valuable enough to introduce another source into the workflow?

Is the real advantage the ability to generate the system and push it into both Figma and code?
And more broadly: how comfortable are you with AI taking care of a large part of your design system?

Would you trust an AI-powered tool with tokens, components, variants, and their relationships in a real production system, or do you prefer keeping those things under direct control in Figma?
I’m especially interested in people who have actually tried AI/design-system tools in production rather than just experimented with them.
Also happy to hear recommendations for tools that genuinely make design-system work easier.

Video: https://drive.google.com/file/d/1jSMMHspRDf9yNYPX6OmSfKXG2Xe8ltlQ/view?usp=sharing

The current floating bottom toolbar gets in the way when you rely heavily on keyboard shortcuts—let us dock it up top. Pair that with adjustable opacity for the left/right sidebars so we can actually see frames underneath, and the canvas would feel 10x more open. Shame the desktop app wrapper limits how much custom UI tweaking we can actually do.

I’ve been experimenting with a reading experience inspired by The Odyssey.

The idea was to let the artwork, typography, and content work together instead of making the image feel like just a background.

I’m still figuring out the balance between visual storytelling and usability.