Migration snapshot
ActivePlatform
a Sizze
Sizze is operating but has significantly pivoted. Originally a Figma-plugin that exported React Native code; now rebranded 'Sizze — AI App Builder' with built-in frontend, backend, and database ('Sizze 3.0,' app.sizze.io). SoftwareWorld (Apr 2026) notes no free version and no documented API. The pivot creates genuine uncertainty about whether the original code-export value proposition still exists in the current product.
Typical timeline
6–10 weeks
Typical cost
$13K–$25K (agency, fixed)
Why teams leave a Sizze
Sizze's migration story is unusual: the platform's core value was always its exit path (Figma → React Native code). The pivot to an AI-hosted product may have eliminated that advantage for new users.
Pivot erases the original export value proposition
Sizze's core appeal was clean Figma → React Native code generation. The new AI-hosted product (Sizze 3.0) may not offer the same export; SoftwareWorld (Apr 2026) notes no documented API, suggesting data portability has regressed.
No API documented for Sizze 3.0
SoftwareWorld (Apr 2026) confirms Sizze 'does not offer an API.' For the hosted version, this means data in the built-in database may be fully locked to the platform with no programmatic export path.
No free tier increases switching cost
Sizze has no free version — ongoing cost commitment with no free experimentation tier. Teams that want to evaluate a migration without canceling their subscription have no low-cost option.
Export ambiguity post-pivot
Whether Sizze 3.0 permits clean React Native export is not clearly documented as of July 2026. Users on the original Figma plugin have a different exit path than users on the new hosted product — and many may not know which they're on.
Sparse external validation of the new product
Limited recent reviews and minimal community discussion of Sizze 3.0 make it difficult to verify quality, stability, and the actual export mechanics of the current product.
What can you actually take with you?
Export depends entirely on product era. Original Figma-plugin users likely have React Native code to work with; Sizze 3.0 AI-hosted users face no documented API and unclear data export — the worst exit of the two paths.
| Asset | Can you export it? | How | Notes |
|---|---|---|---|
| Data | No | Sizze 3.0 has a built-in backend and database with no documented API (SoftwareWorld Apr 2026). No self-service data export path is known. | No API documented means data may be fully locked to Sizze 3.0. Attempt any available manual export (CSV, copy-paste) before migrating. |
| Code | Partial | Original Figma plugin exported Figma/Sizze designs to React Native code — this was the core product value. Whether Sizze 3.0 AI-hosted model still exports clean React Native is not clearly documented post-pivot. | Verify which product you're on before assuming code export exists. For Sizze 3.0 users, treat this as a rebuild, not a port. |
| Design/UI | Yes | Figma file is the source of truth for original-product users. Keep your own Figma file — it is the most portable artifact regardless of product era. | Only applies to original Figma-plugin era. Sizze 3.0 users should document designs via screenshots. |
| Logic/Workflows | No | Not documented for export in either product version. | Logic must be recreated in the target stack from product documentation or screen walkthroughs. |
| Users & Auth | No | Not documented for either version. Password hashes are not exported by any known mechanism. | Plan a forced password reset flow for all users when migrating auth to Supabase. |
Swipe the table sideways to see the full breakdown.
Where each piece moves in code
The migration target is React Native + Expo for mobile and Supabase PostgreSQL for the backend — whether starting from exported React Native code or rebuilding from scratch.
a Sizze
Sizze Figma designs (original product)
In code
Figma file as source of truth; re-export via Anima or hand-code React Native components
Keep your Figma file current and independent of Sizze — it is your most durable asset.
a Sizze
Sizze React Native code export (original)
In code
Expo project — run npx expo install to modernize dependencies, then extend as standard React Native
Assess code quality before committing to port vs rebuild. Generated code may need cleanup.
a Sizze
Sizze 3.0 AI-hosted app screens
In code
Rebuild in React Native + Expo using Figma and screenshots as UI reference
Treat as a no-code-locked platform — rebuild, not port.
a Sizze
Sizze 3.0 built-in database
In code
Supabase PostgreSQL — extract via any available UI export or API access first
No API documented means manual extraction; document data structure from the UI before migrating.
a Sizze
Sizze 3.0 auth
In code
Supabase Auth with forced password reset for all users
Plan in-app announcement and email reset flow into the migration timeline.
a Sizze
App hosting and publishing
In code
Expo Application Services (mobile) + Vercel (web components)
Verify App Store Connect and Google Play Console ownership before starting.
The migration roadmap
The first step in any Sizze migration is a diagnostic: which product era are you on? The answer determines whether you're doing a structured port or a full rebuild.
Phase 1: Product Diagnostic and Asset Extraction
Week 1- Determine product era: open exports and check for .tsx/.js (React Native, original plugin) vs hosted app (Sizze 3.0)
- If original plugin: download all React Native exports and Figma source files immediately
- If Sizze 3.0: attempt any available data export (CSV, screenshot, copy-paste) from the built-in database
- Verify whether the Figma plugin is still functional post-pivot by testing an export today
- Document all screens via screenshots and Figma files — these are primary migration artifacts
Watch out: Do not skip the diagnostic step. Choosing the wrong strategy wastes weeks of rebuild effort.
Phase 2: Code Quality Assessment
Week 1–2- If original export exists: run npm install + expo start on the exported code — does it boot cleanly?
- Assess code quality: is it production-ready or does it need significant cleanup?
- Make port vs rebuild decision based on code quality assessment
- Inventory all screens, navigation flows, and data bindings for rebuild planning
Phase 3: Backend and Auth Setup
Weeks 2–4- Set up Supabase project; design schema from extracted data or screen walkthroughs
- Migrate any extracted data to Supabase PostgreSQL
- Implement Supabase Auth; design password reset flow for existing users
- Set up Next.js or Supabase Edge Functions for any backend logic
Phase 4: Mobile App Build
Weeks 4–9- Port or rebuild React Native screens in priority order
- Connect screens to Supabase backend
- Replace any Sizze-specific dependencies with standard React Native libraries
- Test on iOS and Android via Expo Go and EAS Build
Phase 5: Launch and Cutover
Weeks 9–10- Submit to App Store and Google Play under same bundle ID if possible
- Notify users of the new app version and password reset requirement
- Decommission Sizze subscription after confirming full parity on new stack
- Monitor post-launch for 2 weeks before closing the Sizze account
Three ways to migrate — honestly
Every path has a real trade-off. Here is what each costs, how long it takes, and where it bites.
DIY (with AI tools)
$0–$500 + time
2–5 months part-time
Fits
Founders with React Native experience who are on the original Figma-plugin product and have clean exported code to start from
Risks
If on Sizze 3.0 with no export, scope is much harder to estimate. Generated React Native code may need substantial cleanup before it is maintainable. Community resources for Sizze are sparse.
Freelancer
$4K–$10K
1–3 months
Fits
Apps with fewer than 15 screens and an existing React Native export to work from; teams that can manage freelancer closely
Risks
If export quality is poor, a freelancer may underestimate cleanup scope. Verify code quality before scoping. Limited Sizze-specific precedent means the freelancer is navigating without community guides.
Agency (RapidDev)
Done-for-you$13K–$25K fixed
6–10 weeks
Fits
Production apps where the export path is ambiguous or Sizze 3.0 means a full rebuild is required; teams that need a fixed price and defined handoff
Risks
Minimal — fixed price covers the diagnostic phase through launch. Free scoping call at rapidevelopers.com to assess product era and export viability before committing.
The real risks — and how to defuse them
Data locked in Sizze 3.0 with no documented export
Mitigation: Attempt any available manual export (CSV, screenshot, copy-paste) from the built-in database now. Document data structure from the UI even if you cannot extract raw data.
Figma plugin deprecated or non-functional post-pivot
Mitigation: Test an export from the Figma plugin today. If it no longer works, your Figma file is the only usable design artifact — keep it current and independent of Sizze.
React Native export code quality insufficient for production
Mitigation: Run the exported code locally before committing to a port strategy. If code quality is poor, treat as a rebuild using the export as a logic reference, not a production baseline.
Sunk cost trap from no free tier
Mitigation: Evaluate rebuild cost now — it may be less than the ongoing subscription cost plus accumulated tech debt. A fixed-price rebuild quote gives you a concrete comparison.
No community migration guides for Sizze
Mitigation: Rely on Figma files, screen recordings, and any available exports as your primary artifacts. There is limited precedent from other teams who have migrated off Sizze.
Should you actually migrate?
Migrating is a real project. Sometimes staying is the right call — here is the honest split.
Stay if
- You are on the original Figma-plugin product and the React Native export meets your needs and produces maintainable code
- Your Figma file is kept current, independent of Sizze, and serves as a complete backup for all design work
- App is a simple prototype or MVP where the AI-hosted Sizze 3.0 is still generating value and no production data portability is required
Migrate if
- You need a guaranteed code or data export path and Sizze 3.0 cannot confirm one — no API documented means lock-in
- App is production-critical with real users and the no-API, no-export-documented situation is an unacceptable business risk
- The original Figma-export workflow is no longer available after the pivot and you're now effectively on a no-export platform
- Ongoing subscription cost without a free tier is not sustainable at current app scale
Our honest verdict
Sizze's migration story depends entirely on which product era you're on. Original Figma-plugin users have a real exit via React Native code; Sizze 3.0 AI-hosted users may face a full rebuild. Determine your product era before any other planning — it changes everything.
Do this today: pre-migration checklist
Whatever path you choose, protect yourself first. Work through this before you touch a line of code.
Determine your product: are you on the original Figma plugin or the new Sizze 3.0 AI-hosted app?
The migration strategy is completely different for each product era. This is the single most important diagnostic step.
If original plugin: download all React Native exports and Figma source files immediately
These are your primary migration assets. Download them now regardless of migration timeline.
If Sizze 3.0: attempt any available data export (CSV, screenshot, copy-paste) from the built-in database
With no documented API, manual extraction may be your only data recovery option.
Verify whether the Figma plugin is still functional post-pivot by testing an export today
If the plugin no longer works, Figma files and screenshots become your only design artifacts.
Run the exported React Native project locally: npm install + expo start
Code quality assessment determines port vs rebuild. Do not commit to a strategy before confirming the export runs.
Document all screens via screenshots and Figma files
These are the primary migration artifacts regardless of which product version you're on.
Verify App Store Connect and Google Play Console account ownership
Confirm you control the store listings before the rebuild is complete — store account issues can delay launch.
Frequently asked questions
Can I export my Sizze app code?
It depends on which version you're using. The original Figma plugin exported React Native code — this was Sizze's core value proposition. Whether the new Sizze 3.0 AI-hosted product still provides a clean React Native export is not clearly documented post-pivot. Test an export in the Figma plugin today to check if it still works, and verify which product era your project is on.
Does Sizze have an API for data export?
No. SoftwareWorld (April 2026) confirms that Sizze 'does not offer an API.' For Sizze 3.0 users with data in the built-in database, this means no programmatic export path is documented. Attempt any available manual export (CSV download, copy-paste) from the platform UI before starting migration planning.
What is Sizze 3.0 and how is it different from the original product?
The original Sizze was a Figma plugin that converted designs to React Native code — a clean code-export tool. Sizze 3.0 is a rebranded AI app builder with built-in frontend, backend, and database (app.sizze.io). The two products have very different exit paths: original users likely have React Native code they can export; Sizze 3.0 users may face data and code lock-in.
How long does migrating from Sizze take?
Expect 6–10 weeks with an agency. If you're starting from a clean React Native export from the original Figma plugin, the timeline is closer to 6 weeks. If you're on Sizze 3.0 and facing a full rebuild with manual data extraction, plan for 8–10 weeks. DIY timelines are typically 2–5 months part-time.
What happens to my users' passwords when I migrate?
Password hashes are not documented for export from either Sizze product version. Plan a forced password reset for all users when migrating authentication to Supabase Auth. Build a reset notification email and in-app prompt into your migration launch plan — this is standard for any no-code to code migration.
Is Sizze shutting down?
Sizze is not confirmed to be shutting down as of July 2026 — the platform is active. However, the significant product pivot from Figma-export to AI-hosted creates uncertainty about the product's direction. There is no free tier and no documented API, which means your ongoing investment carries higher lock-in risk than alternatives with cleaner export paths.
What is the best replacement for Sizze's original Figma-to-React Native workflow?
Anima and Builder.io are documented Figma-to-code alternatives. Draftbit offers a visual mobile builder with a clean React Native code export. If you want to own the full codebase from day one, a direct Figma + React Native + Expo workflow with manual component development is the most sustainable long-term approach.
Can RapidDev help with a Sizze migration?
Yes. RapidDev handles both scenarios: ports from original Sizze React Native exports and full rebuilds for Sizze 3.0 users. Fixed-price engagements run $13K–$25K with a 6–10 week timeline. The scoping call starts with a product era diagnostic to determine the right strategy before any work begins. Book at rapidevelopers.com.
We migrate no-code apps to production code
- Fixed price — $13K–$25K (agency, fixed)
- No data loss, no downtime
- You own 100% of the code
30-min call. Quote within 48 hours.