Native app features

Your iOS and Android apps are your web app in a native shell. A few things only make sense in the native app, and there is no settings screen for them: you ask your assistant, and they ship with your next app build.

Push notifications

Floot's built-in push reaches phones as well as browsers. Native push is set up for you when you publish with a store connected: the Apple account for iOS, and Google Play for Android, which needs a paid plan. A build made without the matching store ships without native push. Browser push does not work inside the native app, so the native app needs its own.

Permissions

Floot adds the permissions your app needs on its own: camera and photo access on every iOS build, location and microphone when your code uses them, and notifications when you use Floot's push. The default iOS wording is generic, and Apple rejects apps for it — ask your assistant to write purpose strings that say why your app needs each one, such as "Scan receipts to add them to your expenses."

Things to ask for

Share to your app

Let people share photos, videos, audio, PDFs, text, or links from other apps into yours, from the iOS and Android share sheets. Your assistant also writes the code that receives what was shared.

Work in the background

Run a short piece of your app's code while it is not on screen — when your backend sends a silent push, on iOS and Android, or when iOS gives the app background time. Each wake gets about 25 seconds. The phone decides how often background time comes, and on Android a wake only runs while the app is still alive in the background: once the user swipes it away, wakes are missed.

Status bar style

By default the app sits between solid strips under the status bar and above the home indicator. Ask for a different strip color, light or dark status-bar icons, or edge-to-edge — content running under the bars, with the padding your assistant adds to keep controls clear of them.

iPhone-only

iOS builds support iPhone and iPad by default. Ask for iPhone-only if the iPad layout is not ready. This is one-way: once a version that supports iPad has been released, Apple will not accept an update that drops it, so your assistant asks whether the app is already live before it changes this.

Handled for you

• Apple's privacy manifest entries for the native plugins your app uses.
• The Android status bar and keyboard insets, so nothing hides behind the system bars.
• After your first app build, your project gains static/__dev/native/ios-info.plist and static/__dev/native/android-manifest.xml. Your assistant can edit them for anything else the stores ask for — ask it to read the ios-info-plist or android-manifest guide first.

What counts toward your monthly app builds

• A build counts once it finishes, and while it is still running.
• A build that fails does not count, and neither does one that every connected store turned away.
• A build that a newer one replaced while it was running still counts.
• A test build counts the same as a live build.
• At most 2 app builds run at the same time.
• Builds started during an Action Boost never count — see Build actions.