FluxNative Reviews

I wanted to like FluxNative. And I still want it to succeed.

As someone working with UX design, AI agents and SaaS product development, I see real potential in a platform that turns existing Figma designs into native iOS and Android applications. That's why I purchased Tier 2.

But there's a difference between what a product promises and what the actual experience delivers.

Two days in, and I'm still trying to import my Figma screens.

My project contains 140 carefully designed screens covering multiple user journeys. I expected importing those designs to be one of the simpler steps. Instead, it has become my biggest obstacle.

The Design Sync plugin supports 60 screens per import. Yet after selecting 60, only 20 appeared in my project. I continued importing additional batches, believing everything was transferring correctly.

Support later confirmed a bug where subsequent transfers replaced previous screens rather than adding to them. They released version 1.3.1 to address it.

Unfortunately, the problems continued. After importing approximately 80 screens across two operations, the plugin stopped working again.

The biggest problem isn't just the bugs. It's the unnecessary manual work.

Why should users manually count, select and track hundreds of screens when the plugin should already know which ones have been imported?

It should automatically identify imported screens, select the next 60, track progress, prevent accidental duplicates and allow failed transfers to resume.

Instead, I'm spending time managing imports rather than developing my application.

And 140 screens isn't particularly unusual for a complete product when you account for onboarding, authentication, navigation, settings, different user journeys and interface states.

For an AI development platform designed to save time, this workflow creates the opposite experience.

Design consistency matters too.

When importing completed Figma designs, I expect the AI to treat them as the primary visual source of truth, preserving layouts, typography, colours, components and the existing design system.

I've suggested adding "Figma Import" as a selectable style option so the AI prioritises the original designs instead of introducing unrelated styling.

FluxNative also provides planning and MCP integration, which are valuable capabilities. However, I haven't been able to properly evaluate them within my project because the import problems keep preventing me from progressing.

Now, the positives.

When my initial AI build failed because of a missing or invalid app specification, credits had already been consumed.

I contacted support, and they acknowledged the bug, released a fix and credited 2,368 credits back to my workspace.

I appreciate that. It demonstrates a willingness to take responsibility when something goes wrong.

Their initial support response was also reasonably quick and constructive. However, my latest follow-up has remained unanswered for almost 24 hours at the time of writing, while the import issues remain unresolved.

I understand FluxNative is an early-stage product. Bugs happen, and improvements take time. I'm not expecting perfection.

But fundamental workflows should be reliable enough for customers to actually use and evaluate the product.

Why 3 tacos?

Because the concept has potential, the initial support was constructive, and the team compensated me for the failed build.

But I can't justify a higher rating when I've spent two days troubleshooting Figma imports without reaching actual development.

AI-assisted development should remove repetitive work, not introduce more of it.

Would I recommend it?

For someone experimenting with a small application, FluxNative may be worth exploring.

For designers and product teams bringing complete Figma projects into development, I'd recommend caution until the import workflow becomes more reliable.

I'm not writing FluxNative off. I'm willing to update this review, and hopefully increase my rating, once I've successfully imported my designs, developed my application and launched my first mobile app.

For now, I can only review the experience I've actually had.

And so far, I've spent more time trying to start building than actually building.