You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/marketplace/creators-hub/submission-criteria.md
+25-5Lines changed: 25 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -203,10 +203,30 @@ A seamless and positive test experience is crucial for users to evaluate your Fl
203
203
204
204
#### 4.1 Functional Run Mode Link
205
205
206
-
-**Criteria:** The provided Run Mode link must be active and correctly load a working demo of your project.
207
-
-**Why it Matters:** The Run Mode link is the primary way users can interact with your project before purchasing. A broken or inaccessible link creates a significant barrier.
208
-
-**What To Do:**
209
-
-**Double-check your link:** Before submitting, test the link multiple times to confirm it showcases the experience you want potential buyers to have.
206
+
-**Criteria:** The provided Run Mode link must be active and correctly load a working demo of your project. For mobile-only features or utility libraries that cannot be demonstrated in Run Mode's web environment, you must provide alternative demonstration methods.
207
+
-**Why it Matters:** The Run Mode link is the primary way users can interact with your project before purchasing. A broken, inaccessible, or non-demonstrative link creates a significant barrier to understanding the item's value.
208
+
-**What To Do:**
209
+
-**For Standard Web-Compatible Items:**
210
+
- Double-check your link before submitting to confirm it showcases the experience you want potential buyers to have.
211
+
- Test the link multiple times to ensure consistent functionality.
212
+
-**For Mobile-Only Features:**
213
+
- Create a dedicated demonstration page in your project that explains the mobile-only functionality.
214
+
- Include screenshots, videos, or mockups showing how the feature works on mobile devices.
215
+
- Clearly indicate which features are mobile-only and why they cannot be demonstrated in Run Mode.
216
+
- Optionally, provide a published FlutterFlow web deploy link that can be used instead of the Run Mode URL.
- Create a demonstration page that explains the library's functionality.
219
+
- Show configuration options and expected outcomes.
220
+
- Include visual aids like flowcharts or diagrams to explain the library's operation.
221
+
- Provide example code or configuration snippets.
222
+
- Consider adding debug/test outputs that demonstrate the library is working.
223
+
-**Documentation:**
224
+
- Regardless of the type of item, ensure your documentation clearly explains how to implement and test the functionality in a real mobile environment.
225
+
- Include troubleshooting guides and common implementation scenarios.
226
+
227
+
:::tip
228
+
For items that cannot be fully demonstrated in Run Mode, focus on creating a clear, informative demonstration page that helps users understand the value and implementation of your item. Visual aids, clear explanations, and comprehensive documentation are key to helping users make informed decisions.
229
+
:::
210
230
211
231
#### 4.2 User Sign-In (Anonymous Auth)
212
232
@@ -251,7 +271,7 @@ Building a solid app template goes beyond surface-level design. It's about creat
251
271
#### 5.2 No Pixel Overflow
252
272
253
273
-**Criteria:** Ensure your UI elements are positioned and sized correctly to avoid content overflowing its container, leading to visual glitches / cut off content.
254
-
-**Why It Matters:** Pixel overflows are a sign of UI inconsistencies that can negatively impact the user experience, especially on different screen sizes. Pixel overflow issues can occur in Test Mode when there’s a hardcoded pixel value and not enough space on the screen to render that exact value.
274
+
-**Why It Matters:** Pixel overflows are a sign of UI inconsistencies that can negatively impact the user experience, especially on different screen sizes. Pixel overflow issues can occur in Test Mode when there's a hardcoded pixel value and not enough space on the screen to render that exact value.
255
275
-**What To Do:**
256
276
-**Preview pixel overflows:** Toggle the pixel overflow icon in the top-right of the canvas to see if there are any overflow issues.
257
277
-**Leverage FlutterFlow's layout tools:** Use Expanded and Flex values to help prevent layout issues. Make `Columns` or `Rows` scrollable to prevent overflows. Use auto-sizing text or text clipping where it makes sense. Remove hard-coded width and height where it makes sense.
Copy file name to clipboardExpand all lines: docs/resources/control-flow/backend-logic/api/rest-api.md
+75-23Lines changed: 75 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -569,38 +569,70 @@ Learn more about **[JSONPath](https://www.rfc-editor.org/rfc/rfc9535.html)** and
569
569
:::
570
570
571
571
### Adding JSON Path
572
+
You can effortlessly define and manage **JSON Paths** for your API calls in FlutterFlow to parse and extract the data you need. Once added you can [use](#using-json-path) them as **Predefined Path** while accessing the **JSON Body**.
572
573
573
-
To add JSON path:
574
+
First, [create and test](../api/create-test-api-calls.md) your API call. Inside the **JSON Paths** section, click **+ Add JSON Path**, enter your **JSON Path**, and assign it a name. If the expression is valid, a preview of the response appears under **Response Preview**. Click the **Preview** icon to see the full response. If the response contains a list of items, the **Is List** option will be enabled automatically.
574
575
575
-
1. First, [create and test](../api/create-test-api-calls.md) your API call.
576
-
577
-
2. Inside the **JSON Paths** section, click on the **+ Add JSON Path**.
578
-
3. Enter your **JSON Path** and give it a **Name**.
579
-
4. If you entered the valid expression, you'll see the starting part of the response under the **Response Preview** column. To see the complete response, click on the **Preview** icon.
580
-
5. If the returned response is a list of items, by default, **Is List** will be checked; however, if you want to convert the response into the list explicitly, checkmark it.
581
-
6. We also recommend all the possible JSON paths (under the **Recommended** tab) that might include what you are looking for.
582
-
583
-
1. To add the recommended JSON path, checkmark the **Selected**, open the **Selected** tab,
While accessing values from an API Call, you can either enter the custom JSON path or use the already created JSON path.
594
-
595
-
To use the already added JSON path:
607
+
While accessing values from an API Call, you can either enter the custom JSON path or use the [predefined JSON path](#adding-json-path).
596
608
597
-
1. Select your API response.
598
-
2. Set the **API response Options** to **JSON Body**.
599
-
3. Set the **Available Options** to **JSON Path**.
600
-
4. Set the **JSON Path Name** to the one that you created earlier.
609
+
To use a predefined JSON Path, first, select your API response. Then, set the **API Response Options** to **JSON Body** and the **Available Options** to **JSON Path** or **Predefined Path**. Finally, specify the JSON Path Name or select from the predefined JSON Path to map the extracted data for use in your app.
Why is my Predefined Path not showing any options?
780
+
</summary>
781
+
<p>
782
+
This often happens if you added the Predefined Path but forgot to save the API call in FlutterFlow. Ensure you click Save after making any changes to your API call so FlutterFlow can properly recognize and display your predefined paths.
783
+
</p>
784
+
</details>
785
+
786
+
<details>
787
+
<summary>
788
+
Why am I getting a “Current variable is not valid” error?
789
+
</summary>
790
+
<p>
791
+
This error typically indicates that the widget isn’t receiving the data type it expects. For example, passing a list of colors directly to a text widget will trigger the error. In such cases, convert or supply the data as a string (or another compatible type) so the widget can properly display it.
0 commit comments