multiple firebase and supabase connections
It wasn't meant to be a complaint, more like a frustrated heads up. Happy to pay for a good product (even if my Firebase / Firestore doesn't work, like others: all requests and up in "not found, error 5").
A bit more information on the pricing would be benefitial, I am a Indy by night and Product Manager for App development by day, so perhaps my way of working is different than others, that's why I asked. I have a couple of smaller experiments and app projects running across multiple providers, and thought consolidating some projects into one Pro Plan will facilitate the backenend needs for all projects (I have a backend developer background, but I LOVE the light and crispyness of Rowy and Buildship for my backend needs, can't be bothered to do all the basework from scratch)
A folder structure would be a huge benefit for organzing different areas of your api.
I am still not sure how to deal with multiple data vendors, like multiple SB instances or using the build in FB instance with a Flutterflow project or not? Are there any best practises?
A bit more information on the pricing would be benefitial, I am a Indy by night and Product Manager for App development by day, so perhaps my way of working is different than others, that's why I asked. I have a couple of smaller experiments and app projects running across multiple providers, and thought consolidating some projects into one Pro Plan will facilitate the backenend needs for all projects (I have a backend developer background, but I LOVE the light and crispyness of Rowy and Buildship for my backend needs, can't be bothered to do all the basework from scratch)
A folder structure would be a huge benefit for organzing different areas of your api.
I am still not sure how to deal with multiple data vendors, like multiple SB instances or using the build in FB instance with a Flutterflow project or not? Are there any best practises?
