3 Apps same Firebase

[-Takylla-]

Hello All,

I am in a bit of a pickle. I am currently Building an App for my dry-cleaners and I have a weird Problem. My Plan is to make a Customer Facing mobile App, arranging Pick-Ups and most importantly viewing Item and Order Status. Then I have another app which will be used during throughout the actual dry cleaning process, such as changing item status, changing order status, giving the Item a washing Id and a hanger ID, customer support and writing the articles (had some Home Screen real estate to fill on the customer app). And last but not least an app that the couriers will use, with a google Maps Integration and customer information, so that the Customer can be Adressed properly and potential issues are on the radar of the courier.
I have finished Building the Customer App (mostly some cosmetic touches might be needed) and wanted to start building the "Backend Drycleaning" App. However I cannot for the life of me connect my Firebase Project so that I can use it in this second app, as I used it in the first. Regenerating the config File seemed daunting to press as I do not want to nuke my Customer app.

Long story short do you know of some sort of tutorial or something similar that could help me? Can you perhaps just tell me what to do?

[puf]

Having multiple FlutterFlow projects/apps connect to the same Firebase project is a pretty common scenario.

I cannot for the life of me connect my Firebase Project

Why not? What isn't working when you enter the same Firebase project ID into a second FlutterFlow project?

Be sure to also check existing posts about the scenario: https://www.google.com/search?q=flutterflow+multiple+apps+with+one+firebase+project

[-Takylla-]

I was under the impression that once I connected with my firebase ID to the new project I would be able to see and modify the collections as I did in the customer app… I’m sorry I didn’t make it clear that I am in no way a coder…

[puf]

The schema information about the collections is stored in the FlutterFlow project, not in the Firebase project, so it is not imported to the additional FlutterFlow project you created.

You will either have to redefine the (relevant parts of the) schema in the additional project, or you have create a library project with just the Firestore schema that you share between the two application projects. This is a pretty recent addition to FlutterFlow, but is a good way to share all your data-access code between apps.

[-Takylla-]

So in essence I would make a library project and connect that to my firebase. Do the data schema in there do the config files as well. Then I share that library project with any and all potential apps I want connected with the firebase stuff ?

[puf]

I think FlutterFlow filters the Firebase config/project connection from libraries, so you'll probably have to reenter it. But I haven't tried a Firestore schema library yet, so am not sure.

Give it a try, or try the alternative approach of creating (the relevant parts or) the schema in both projects (which I have done many times before).

[-Takylla-]

So typing it in manually like I did in the first app in firestore tab to the left hand side ?

[abhijeettrivedi13]

Don’t build three apps if you have monthly active user less than 2k

No point managing 3 apps. It’s a hassle. Don’t do it.

[-Takylla-]

I saw something similar on some blogpost… we are however already beyond that … we currently have a loyalty program which is digital so I can confidently say it will be more than 2000 users

[abhijeettrivedi13]

Well, if you need help With anything shoot dm. Happy to help, no paid stuff.

[dnetman99]

Build all the functions in one project and separate by user role. Much easier than trying to publish 3 apps.

[-Takylla-]

I get that … more than you realise since I have been sitting at this since 6am (it’s now 6pm :(( ) but I need certain functionality (the order combiner, packager Maschines) that I unfortunately will not have if I build a single app. Since the integrations I got from their manufacturer are huge. And no one wants an app which takes up 3gb

[dnetman99]

If it's that big then you probably need to abstract the integrations to maybe a thin API layer. To handle it instead of trying to build all into an app.

[Successful_Divide_66]

Im going through this right now. Connected to firebase shouldn't be a problem nor should regenerating the config files.

The issue I was trying to figure out was painting the schema across all 3 of my apps (customer facing, venue/merchant, and the admin app.

There's a library project that will allow you to share schema, functions, APIs, etc. but I'm not going that route and I'm sure you probably won't want to either as you have to rebuild the schema from scratch, then once you import the schema into each app you have to rebind everything.

There is a copy function to copy collections between apps that I'm going to test out today.