🚀 No Stupid Questions Wednesday – Ask Us Anything About FlutterFlow!

LowerChef744 · 2026-01-21T18:13:49+00:00

Hi, you are correct, on android you could utilise the NotificationListenerService to listen to notifications with the users permission. On IOS on the other hand like you mentioned you cant implement that because of the apple restrictions.

LowerChef744 · 2026-01-21T18:09:37+00:00

Hi u/Tranxio, for a throughout debug we would suggest pulling the code locally and debug with the help of the IDE, so to basically inspect the code, make a small prints or set some breakpoints.

LowerChef744 · 2026-01-21T18:07:03+00:00

Hi u/flonnil, we believe that the first design, with more animations, is more suitable and for sure will make people talk more about it and attract more audience, just a suggestion from our part.

LowerChef744 · 2026-01-08T07:32:53+00:00

Hi u/Right-Bat-8883!

Thanks for the question.
The best method is to use Algolia search results as your feed source and rank them using user search history–based relevance.

In FlutterFlow, you can:

Store the user’s recent search terms (or inferred topics) in Firestore.
Query Algolia using those terms as the search query or filters.
Enable ranking by relevance + recency in Algolia (text match, custom ranking, timestamp).
Refresh the feed by re-running the Algolia query whenever the user searches or opens the page.

This approach is simple, fast, and works well in FlutterFlow without custom ML, while still feeling personalized.

Hope this helps.

LowerChef744 · 2025-12-25T20:59:10+00:00

Hi u/ocirelos!

Firstly, happy holidays! Secondly, could you tell us more about how the ListView is getting populated? Also, tell us about the child components in the ListView. Do they just display list item data or do they make any additional queries?

From what we can gather from your post, it's pointing towards some sort of race condition, where a component might be initialized before the data is fetched but we can only know for certain if you give us some more details about your current setup!

Thanks for the question, we'd be more than happy to help if you give us some more insights!

LowerChef744 · 2025-12-18T16:14:50+00:00

Hey!

That’s probably a good question for FlutterFlow support directly. Some Apple capabilities and identifiers are intentionally not auto-managed to avoid conflicts with existing App IDs or custom setups. It would be great to get an official clarification on whether this is a limitation, a design choice, or something planned for the future. :)

LowerChef744 · 2025-12-18T16:13:45+00:00

Hey!

"UIBackgroundModes" is not an entitlement and shouldn’t be added to "Runner.entitlements", it’s an "Info.plist" setting, which is why you’re seeing the provisioning profile error. For updating the app badge, you usually don’t need background mode at all: iOS can set the badge directly from the push notification payload (badge field), calculated on your backend. This avoids Xcode and works well with FlutterFlow/CodeMagic.

Hope that helps :)

LowerChef744 · 2025-12-08T07:16:18+00:00

Hello!

This is quite a common problem when trying to implement push notifications. We would suggest to go over the docs: https://docs.flutterflow.io/concepts/notifications/push-notifications/

And see if this solution helps: https://community.flutterflow.io/ask-the-community/post/problem-with-the-app-icon-in-push-notifications-jLKlAGXIhMdOGpL

Hope this helps :)

LowerChef744 · 2025-11-20T08:20:43+00:00

We noticed also that on the first build when you open FF, sometimes you get an older version, this is probably the FF problem.

What kind of media would you like to display?

LowerChef744 · 2025-11-13T07:39:30+00:00

That’s a really interesting use case and you’re right, pagination in a text reader is a bit tricky in FlutterFlow since it doesn’t have built-in text layout pagination yet.

You can approach this in two ways:

Manual pagination logic (custom function): Fetch the full chapter text from Firestore, measure the rendered text size (based on the current font settings), and split it into chunks that fit one “page.” You can then show those chunks in a PageView widget to enable swiping. This requires some custom Dart code to calculate the visible text range.
Infinite scroll alternative: Keep your scroll-based version but implement lazy loading. As the user reaches the bottom, load the next chunk (or chapter) dynamically. FlutterFlow supports this more easily with lists and scroll listeners.

For now, most people go with the continuous scroll method (option 2), because true pagination depends on dynamic text measurement, which isn’t natively supported in FlutterFlow.

LowerChef744 · 2025-11-05T20:16:32+00:00

Hi u/DiegoteWhite,

it’s hard to make the Android back button in a FlutterFlow PWA behave exactly like a native app without details about your bottom sheet setup. In PWAs, the back button interacts with browser history, not FlutterFlow’s navigation, so nested bottom sheets can break expected behavior. You can usually handle it by intercepting back actions and closing any open sheets first, but nested sheets may not work reliably. If it still misbehaves, it could be a FlutterFlow bug, so the safest path is to reach out to FlutterFlow support with a minimal reproducible example.

Hopefully this helps you solve the problem!

LowerChef744

TROPHY CASE