What would be a better setup for migrating our copywriter app from Bubble to Webflow, considering our requirements for saving user-generated content and potential limitations with Airtable's number of records?

To migrate your copywriter app from Bubble to Webflow, you'll need a revised architecture since Webflow doesn’t support logic-heavy apps natively. The main concerns you’ve mentioned are saving user-generated content and Airtable’s record limitations, so here’s a better setup:

​

1. Use Webflow for Front-End UI Only

​

• Design all public-facing pages in Webflow, leveraging its CMS for static content (e.g., blog, help pages).
• For dynamic or user-specific actions (e.g., creating/saving copy), integrate third-party backends to handle logic and storage.
• Use Memberstack or Outseta for authentication to restrict access and show user-specific data.

​

2. Use Xano as Your Scalable Backend

​

• Replace Airtable with Xano, a no-code backend with higher scalability and a full database + API layer.
• Xano allows complex data types and relationships, and you won’t hit Airtable’s limit of ~50,000 records easily.
• Create APIs in Xano to store, update, and retrieve user-generated content.

​

3. Connect Webflow and Xano with Custom Embeds or JS

​

• Use custom JavaScript snippets in Webflow pages to call Xano APIs via fetch() or axios.
• Content creation forms in Webflow will submit data to Xano via API requests, not via Webflow forms.
• Store/refresh user tokens securely for authenticated requests.

​

4. Optional: Use Wized for App Logic Integration

​

• If you prefer a more visual approach, integrate Wized, which connects Webflow with Xano and handles authentication, conditional logic, and data binding.
• Wized allows near-native Webflow UX with backend functionality, ideal for apps like yours.

​

5. File Storage (if needed)

​

• If users upload files (e.g., documents), use Uploader by Uploadcare or Cloudinary and link file URLs to user entries in Xano.
• Avoid storing files in Webflow or Airtable due to file and bandwidth constraints.

​

6. Consider Future Expansion

​

• If long-term growth is a concern, Xano or Supabase gives you flexibility to scale into advanced use cases (e.g., analytics, rate-limiting, AI integrations).
• You can later migrate the front end to a more dynamic framework (e.g., Next.js), while still using the same backend.

​

Summary

​

Use Webflow strictly as the front-end, pair it with Xano for scalable backend storage and logic, and optionally use Wized to bridge them. Avoid Airtable due to record limits for user-generated content and opt for a backend that can grow with your app.