FileBridge
LocalRemoteNew name, new logo, new website, but the same app.
Why did I change the name?
I liked the name FileBridge, but a couple of days after the launch, Google Search Console was showing me something I didn't like.
I started getting impressions on a 3-day-old website with 0 DR. People were searching for FileBridge on Google. I knew there was something on the .com domain that was also called FileBridge, but I never went deep enough to check it out properly. The impressions continued to rise, and at some point I decided to check if the name was safe to use.
So I ran those 3 checks:
- Asked Claude about the nameThere was a document management portal called FileBridge (the app on .com) and a registered trademark in the US and Canada. I don't know much about trademarks, but Claude suggested not using the name.
- Looked it up on Google TrendsPeople were searching for FileBridge, and it wasn't my app.
(Screenshot from Google Trends showing the search interest for FileBridge) - Checked which filebridge domains were takenInstant Domain Search showed me 14 taken domains with the name FileBridge. That gave me a rough idea of how available and how popular the name was.
All in all, it was obvious that I should not use the name FileBridge. People already knew it as a different product, and it was a registered trademark. Better to change it now than later.
Why LocalRemote?
I changed the marketing angle a bit, and LocalRemote is now "the file manager for developers". So I wanted a slightly nerdy name to match.
LocalRemote describes what the app does. It is a dual-pane file manager, with your local files on one side and a remote server on the other. Local and Remote, side by side. 🙂
It also passed every check that FileBridge failed:
- not taken by another product
- no existing brand showing up when you search for it on Google
- a free .app or .dev domain
What changes for existing users?
Almost nothing. LocalRemote is the same app, and version 1.0.0 is the first one with the new name and icon.
- your license key still works
- your saved workspaces and connections are still there
- just update FileBridge to version 1.0.0, and it becomes LocalRemote
If something does not work the way it did before, just reply to your purchase email and I will sort it out.