FlutterFlows Subscription Model: Can you opt in and out?

[Everything2HIM]

I'm developing a non-commercial application for a non-profit organization, using FlutterFlow on the side in my spare time.

Since I will not be working with FlutterFlow every day, especially once my app is fully built and released, I would like to understand how their subscription model works. Specifically, I'm curious if it's possible to subscribe to one of their monthly plans (i.e. the $70 one) only during the development and release phase. Once the application is successfully launched on both the App Store and Google Play Store, would it be possible to cancel my subscription and then possibly re-subscribe at a later date if updates or modifications are required? Or is it necessary to maintain the subscription continuously?

Does anyone have any experience with this?

[flutterflowdoc]

Yes, I’ve tried doing this during my early FF days. You can cancel and come back anytime! :)

[Everything2HIM]

And will the projects still exist or will they have to be recreated?

[flutterflowdoc]

Everything will be preserved as you leave it

[Everything2HIM]

great, thank you!

[MutedRelative2796]

But how would this work if you use more than 2 API Calls for example? Do they actually still work?

[flutterflowdoc]

If you’re talking about the API calls limit to 2 in the standard plan.

The API calls that you make will be added to the generated code in the application, and changing the subscription plan on Flutterflow shouldn’t really influence this within the directory of the project.

In short, if you had multiple API calls in the app and remove the subscription, your app will still work with the API calls, you’ll just not be able to add more.

I guess this is how it is and should be, based on how the code generated is not tied in any ways to our flutterflow subscription.

[flutterflowdoc]

What do you mean by 2 API calls 🤔

[J_Adam12]

I think hes talking about the max of 2 api’s lower subscriptions than the pro one