✅ Quick Summary

Once you export your Floot project's source code to GitHub with Push44, you own the actual markup and styling — meaning you can remove or customize the badge exactly as you'd edit any other piece of your app's HTML/CSS.

The Problem

The default badge is fine for prototypes, but many builders want a fully white-labeled app before sharing it with customers or clients.

How Push44 Solves It

Once you export your Floot project's source code to GitHub with Push44, you own the actual markup and styling — meaning you can remove or customize the badge exactly as you'd edit any other piece of your app's HTML/CSS.

Step-by-Step Guide

1

Export your Floot project with Push44

Connect your Floot session token and push your project's full source code to a GitHub repository.

2

Locate the badge markup

Search your exported code for the badge component — it's typically a fixed-position element injected near the root of your app layout.

3

Remove or restyle it

Delete the badge component, or restyle it to match your brand, directly in your codebase.

4

Deploy your customized version

Since you now have the full source code in GitHub, you can deploy it anywhere — Vercel, Netlify, or your own infrastructure — without the badge.

Pro Tips

  • Check Floot's terms of service regarding badge removal on apps still hosted directly on Floot's infrastructure.
  • Exporting with Push44 is the cleanest way to get pixel-level control over every part of your app's UI.

Common Mistakes to Avoid

⚠️ Watch Out For
  • Trying to hide the badge with CSS overrides inside Floot's own editor, which can be fragile and get reset on republish.

Ready to Export?

Push44 is free, open source, and takes under 2 minutes to set up.

Start Exporting Now → View on GitHub

Frequently Asked Questions

Does removing the badge violate Floot's terms?
This depends on Floot's current terms of service and your plan — always check Floot's own policies before making branding changes to apps hosted on their platform.
Is badge removal easier after exporting to GitHub?
Yes. Once your code lives in your own GitHub repo and you deploy it independently, you have full control over every element, including any injected badges.