Merge branch 'main' into feature/config-files-build-gradle

Author: pinkeshmars

docs/accounts-billing/new-pricing-comparison.md

@@ -342,7 +342,7 @@ export const PricingToggles = () => {
             <td>Automated Testing<br/><span className="feature-description">Run automated tests on your applications</span></td>
             <td>❌</td>
             <td>❌</td>
-            <td>❌</td>
+            <td>1 test per project</td>
             <td>Up to 3 tests per project</td>
             <td>Unlimited tests</td>
           </tr>
@@ -380,7 +380,7 @@ export const PricingToggles = () => {
           </tr>
           <tr>
             <td>Cloud Functions<br/><span className="feature-description">Write and deploy Firebase Cloud Functions directly from FlutterFlow</span></td>
-            <td>❌</td>
+            <td>✅</td>
             <td>✅</td>
             <td>✅</td>
             <td>✅</td>

docs/ff-concepts/adding-customization/code-file.md

@@ -459,4 +459,15 @@ You can access the custom enums from **Set from Variable** menu > **Custom Enum*
 - Keep your custom class files modular and focused; ideally one class per file for better organization and reusability.
 - Avoid advanced Dart features that are not supported by FlutterFlow’s parser, such as generics or function-typed fields.
 - Re-parse your code after making changes to ensure FlutterFlow updates the parsed structure correctly.
-- Document your code with comments to make your custom classes easier to understand and maintain over time.
+- Document your code with comments to make your custom classes easier to understand and maintain over time.
+
+## FAQs
+
+<details>
+<summary>
+Can I add Custom Classes (Code Files) in a Library Project?
+</summary>
+<p>
+Yes, you can. When a Library Project is imported, any custom code files you’ve defined will be parsed, and the resulting classes will be available for use in the consuming project.
+</p>
+</details>

docs/ff-concepts/adding-customization/custom-code.md

@@ -68,7 +68,9 @@ necessary code.
 This can significantly speed up the building process and reduce the need for in-depth programming
 knowledge, making it especially useful for custom functions and actions.
 
-**Limitation:** The prompts are limited to 100 characters currently.
+:::info[Limitation]
+Your prompt must be at least 3 words and no more than 500 characters.
+:::
 
 <div style={{
     position: 'relative',

docs/ff-concepts/layout/responsive-layout.md

@@ -196,4 +196,58 @@ To implement this, we can go to its widget properties and toggle the device icon
 
 And now you have a more responsive screen for this shopping app use case that looks good in both mobile and desktop formats.
 
-With these adjustments, your shopping app now boasts a highly responsive screen that seamlessly adapts to both mobile and desktop formats. This ensures an optimal user experience across all devices, maintaining both functionality and aesthetic appeal.
+With these adjustments, your shopping app now boasts a highly responsive screen that seamlessly adapts to both mobile and desktop formats. This ensures an optimal user experience across all devices, maintaining both functionality and aesthetic appeal.
+
+## Responsive Value
+
+**Responsive Values** allow you to define different property values, such as widths, heights, font sizes, or padding, for different device sizes (mobile, tablet, desktop, and wide). At runtime, your app evaluates the screen width and automatically applies the appropriate value based on your configurations.
+
+:::info[possible use cases]
+
+- **Adaptive Layouts**: Automatically adjust element sizes to deliver a consistent UI across devices.
+- **Better Readability**: Increase font size on larger screens to improve legibility.
+- **Improved Spacing**: Use different padding or margins on tablets and desktops to optimize content flow.
+
+:::
+
+To set a responsive value, select a widget and choose a property that supports responsiveness. Click **Set from Variable > Responsive Value**, then enter different values for each screen size:
+
+- Mobile (below `Breakpoint Small`)
+- Tablet (below `Breakpoint Medium`)
+- Desktop (below `Breakpoint Large`)
+- Wide (above `Breakpoint Large`)
+
+As you preview on different devices, the property will automatically adjust based on the selected screen size.
+
+:::tip[Customizing Breakpoints]
+
+You can adjust the default screen size breakpoints (mobile, tablet, desktop, wide) in FlutterFlow’s Theme Settings. See how to [**Customize Breakpoints**](#customize-responsive-breakpoints).
+
+:::
+
+
+<div style={{
+    position: 'relative',
+    paddingBottom: 'calc(56.67989417989418% + 41px)', // Keeps the aspect ratio and additional padding
+    height: 0,
+    width: '100%'}}>
+    <iframe 
+        src="https://demo.arcade.software/0XfY0BCqlcIrsXhOGlCh?embed&show_copy_link=true"
+        title=""
+        style={{
+            position: 'absolute',
+            top: 0,
+            left: 0,
+            width: '100%',
+            height: '100%',
+            colorScheme: 'light'
+        }}
+        frameborder="0"
+        loading="lazy"
+        webkitAllowFullScreen
+        mozAllowFullScreen
+        allowFullScreen
+        allow="clipboard-write">
+    </iframe>
+</div>
+<p></p>

docs/ff-integrations/authentication/firebase-auth/apple-login.md

@@ -269,10 +269,14 @@ For testing your app on a real device, you must configure the project in Xcode.
 
 Here's how you configure your project in Xcode:
 
-1. Open your project in Xcode. If you are using Android Studio, right-click on the **ios** folder, find **Flutter,** and then click on the **Open iOS module in Xcode**.
+1. From the Local Run, [open your project in Xcode](../../../testing-deployment-publishing/running-your-app/local-run.md#access-project-code). 
+:::tip
+If you are using Android Studio, right-click on the **ios** folder, find **Flutter,** and then click on the **Open iOS module in Xcode**.
+:::
 2. In Xcode, click on **Runner** (left side menu) and then select the **Signing and Capabilities** tab.
 3. We recommend choosing the **Automatically manage signing** option. This will auto-create the profiles, app ID, and certificates required to build and run your app. If you don't, you'll have to [manually create a 'provisioning profile'](https://blog.codemagic.io/distributing-native-ios-sdk-with-flutter-module-using-codemagic/) and then add it in the Xcode.
 4. Under the **Signing** section, find the **Team** dropdown and select your team.
+5. Use [Local Run](../../../testing-deployment-publishing/running-your-app/local-run.md) to test the app on a real device.
 
 <div style={{
     position: 'relative',

docs/ff-integrations/authentication/firebase-auth/facebook-login.md

@@ -270,7 +270,7 @@ To let users log out of your app, you can use the [Logout](auth-actions.md#logou
 
 ### 9. Prepare to test the app
 
-Facebook Sign-In functionality does not work in Run or Test Mode and can only be tested on a real device or emulator.
+Facebook Sign-In functionality does not work in Run or Test Mode. You can test your app on a real device or emulator using FlutterFlow’s Local Run. Follow the [Local Run documentation](../../../testing-deployment-publishing/running-your-app/local-run.md) and see [how to set up a physical device](../../../testing-deployment-publishing/running-your-app/local-run.md#setup-physical-device) to start testing.
 
 ### 10. Verify user creation
 

docs/ff-integrations/authentication/firebase-auth/google-login.md

@@ -99,7 +99,11 @@ If you haven’t already, see how to [create *users* collection](auth-initial-se
 To let users log out of your app, you can use the [**Logout**](auth-actions.md#logout-action) action.
 :::
 
-## Test Google Login in various platforms
+## Test Google Login
+
+### Running on Device
+To test during development, you can run your app locally using FlutterFlow’s Local Run. Follow the [Local Run documentation](../../../testing-deployment-publishing/running-your-app/local-run.md) and see [how to set up a physical device](../../../testing-deployment-publishing/running-your-app/local-run.md#setup-physical-device) to start testing.
+
 
 ### Running on Test Mode/Run Mode
 

docs/ff-integrations/authentication/firebase-auth/phone-login.md

@@ -306,7 +306,7 @@ While releasing the app, make sure to [**get the key from the Play Console**](au
 
 
 1. Open the [Google Developers Console](https://console.developers.google.com/) (Make sure your project is selected in the dropdown at the top), Click on the **Library** menu on the left, search for the **Google Play Integrity API,** and enable it.
-2. Now, download and test the app using the instructions [here](../../../testing-deployment-publishing/exporting-code/ff-cli.md).
+2. Now, you can test your app on a real device using FlutterFlow’s Local Run. Follow the [Local Run documentation](../../../testing-deployment-publishing/running-your-app/local-run.md) and see [how to set up a physical device](../../../testing-deployment-publishing/running-your-app/local-run.md#setup-physical-device) to start testing.
 
 <div style={{
     position: 'relative',

docs/ff-integrations/authentication/supabase-auth/google-supabase.md

@@ -392,7 +392,7 @@ To let users log out of your app, you can use [this](auth-actions.md#log-out-act
 
 Currently, testing the Supabase Google login feature isn't possible in Run or Test modes due to certain restrictions. But, for web platform testing, you can publish your app with a subdomain using our [web publishing](../../../testing-deployment-publishing/publishing/web-publishing.md) feature.
 
-For testing on mobile, you can use our [Local Run](../../../testing-deployment-publishing/running-your-app/local-run.md) feature.
+You can test your app on a real device or emulator using FlutterFlow’s Local Run. Follow the [Local Run documentation](../../../testing-deployment-publishing/running-your-app/local-run.md) and see [how to set up a physical device](../../../testing-deployment-publishing/running-your-app/local-run.md#setup-physical-device) to start testing.
 
 
 ### 9. Verify user creation

docs/ff-integrations/authentication/supabase-auth/supabase-apple-auth.md

@@ -200,7 +200,10 @@ To test your app on a real device, you must configure the project in Xcode. This
 
 Here's how you configure your project in Xcode:
 
-1. From the Local Run, [open your project in Xcode](../../../testing-deployment-publishing/running-your-app/local-run.md#access-project-code). **Tip**: If you are using Android Studio, right-click on the **ios** folder, find **Flutter,** and then click on the **Open iOS module in Xcode**.
+1. From the Local Run, [open your project in Xcode](../../../testing-deployment-publishing/running-your-app/local-run.md#access-project-code).
+:::tip
+If you are using Android Studio, right-click on the **ios** folder, find **Flutter,** and then click on the **Open iOS module in Xcode**.
+:::
 2. In Xcode, click on **Runner** (left side menu) and then select the **Signing and Capabilities** tab.
 3. We recommend choosing the **Automatically manage signing** option. This will auto-create the profiles, app ID, and certificates required to build and run your app. If you don't, you'll have to [manually create a 'provisioning profile'](https://blog.codemagic.io/distributing-native-ios-sdk-with-flutter-module-using-codemagic/) and then add it in the Xcode.
 4. Under the **Signing** section, find the **Team** dropdown and select your team.