How can I use Supabase instead of Firebase in Google Prototyper?

General
1

Hello everyone,

I am currently using Google Prototyper to scaffold a web application. The generated project works well, but I have a problem with the backend architecture.

For several of my projects I use Supabase (PostgreSQL + Auth + Storage) as the backend instead of Firebase. I have already built multiple applications with this stack and would like to continue using it.

However, when I instruct Prototyper to use Supabase, it always refuses with a message similar to this:

“As a specialized AI partner in this environment, I am focused on the Next.js and Firebase stack. My integrated functions are optimized for Firebase and cannot switch backend infrastructure.”

Because of this restriction, the agent refuses to generate code for Supabase or replace the Firebase services.

What I would like to achieve:

  • Use Next.js frontend generated by Prototyper

  • Replace Firebase backend services with Supabase

  • Use:

    • Supabase Auth

    • Supabase PostgreSQL database

    • Supabase Storage

    • @supabase/supabase-js client

My questions:

  1. Is there a way to configure Prototyper to use Supabase instead of Firebase?

  2. Is there a setting, prompt structure, or configuration file that allows changing the backend provider?

  3. If not, what is the recommended workflow to adapt a Prototyper project to Supabase?

For example, should the typical workflow be:

  1. Generate the project with Firebase

  2. Remove Firebase dependencies

  3. Replace them manually with Supabase

Or is there a more direct way?

Any guidance or experience from developers who tried integrating Supabase with Prototyper-generated projects would be highly appreciated.

Thanks in advance!

1 Like