Quick update: 82 of the 100 founding places are taken, so 18 are left.
Founding members are the first 100 people to finish setup (verify your email and set up your first device). They get 100 MB files, 5 GB of storage and 10 devices, free for as long as fwd runs. Everyone else gets the free plan: 25 MB files, 1 GB and 5 devices.
About 270 invites are out now and most haven't been used yet, so the last 18 will probably go fast. If yours is sitting in your inbox, now's the time. An invite on its own doesn't hold a place.
No invite yet? Join the waitlist at usefwd.io. More invites go out this week.
Hi, just checking to see if I'm doing something wrong in the setup. Does the chrome extension count as 1 device even though it's different computers' chrome browsers.
Meaning if I want multiple computers to use FWD I should use it through the mac app. Thanks!
Edit: I initially installed a chrome extension on my MacStudio. Today when I installed it on my MBP, on the setup screen, I got some kind of prompt asking if I want to replace a device. It wasn't named MacStudio, but was short string of characters. Afterwards, the device name on my MBP was MacStudio.
Edit 2: 100% my bad! I just checked on my phone and all 3 devices I setup shows up individually. Sorryyyyyy
Apologies for the radio silence over the last couple of weeks. I've had my head down deep in code, and I'm thrilled to finally come up for air with a big progress update on fwd:
My number one priority from the start was getting the security model right. I'm happy to report that the full End-to-End Encryption (E2EE) system is now completely implemented. This was by far the most challenging part of the build, and it took the most time because getting it right was non-negotiable. Every note, link, or file you send through fwd: is encrypted on your device and can only be decrypted by your other trusted devices. The encryption also covers the notifications and SMSs that will be synced across devices.
With that security foundation in place, the apps themselves have been coming together quickly. Here's where we stand:
โ The Android & iOS apps are almost feature-complete.
๐ I've officially started the submission process for the Google Play Store and the Apple App Store!
โ The Chrome extension is ready and working.
โ You can securely pair up to 10 devices to a single account.
Currently, my focus is on building the native macOS menu bar app to make the desktop experience as seamless as possible.
Submitting to the app stores is one of the final major hurdles. This means we are getting incredibly close to being able to send out the first private beta invites.
I'm so excited to get this into your hands. Let me know in the comments: What platform are you most excited to try fwd: on first?
I know that everyone here has been on the same frustrating search for a solid Pushbullet replacement. It's the reason this community exists.
To centralise all that collective knowledge and experience, I've put together a comprehensive guide on the current landscape of alternatives. It covers the technical problems (like Manifest V3), reviews the common workarounds, and lays out the vision for fwd:.
A lot of you asked for it, here, by email and from inside the app. Every one of those asks went on the roadmap, and every time I opened it, Firefox was sitting near the top, waiting. Today I finally get to answer all of you with a link instead of "it's on my list."
It does what the Chrome extension does, end-to-end encrypted, in Firefox 142 or later on Windows, Mac or Linux, and in browsers built on it like Zen and LibreWolf. Firefox does a few things its own way (forwards arrive while it's open, and notifications have no buttons): the help page has the details.
Already use fwd? Install it, sign in, and approve it from one of your devices. On the waitlist? Your invite works in Firefox too.
If you asked for this, please give it a go and tell me what breaks: comment here, use Send feedback in Settings, or email [email protected].
I have been using the app on my Android and my personal devices via Chrome Extension. However, I am not able to use on my Corporate devices because of Extension Restrictions.
Therefore, do you envisage having a a web UI, like https://www.pushbullet.com/ such that users can still benefit from "usefwd" on Corporate devices which block extensions.
The second batch of invites went out tonight, so about 160 of you now have access to fwd. If you're expecting one and can't find it, check spam or promotions for an email from "Hamza at fwd".
Thanks to everyone who's tried it and told me what broke. Here's what came up and what changed:
Phones couldn't scan the pairing QR code. The code was too small on some screens. It's bigger now in the Chrome extension and the Mac app.
Sharing the recovery key from Android didn't work well. The recovery key screen now has Copy, Save and Print like the other apps, and asks you to confirm you've saved it. It's out on Mac and rolling out on Android now. The extension gets it in its next update.
Filtering search by Images or PDFs showed the wrong items. Fixed on Android and Mac. The Chrome update with this fix is with Google for review.
Both of the first two were fixed the day they came in. Keep them coming.
On Android: install from the Play Store app on your phone, signed in with the Google account you joined the fwd-beta group with. The Play website often says "not found" for apps that are still in testing. The Android app can also tell you when an update is ready now.
Creator of fwd: here. Thank you for being here and for being a part of this journey from the very beginning.
If you're here, you're probably like me: a long-time user of tools like Pushbullet who felt completely left behind. For years, we had a seamless workflow, a digital glue that just worked. Then, it broke.
The Chrome extension died, the apps started to feel abandoned, and the alternatives were either buggy or missing core features. The silence from developers was deafening. This isn't just a feeling; it's a documented reality. This collage of unanswered pleas from the Chrome Web Store is the reason this project, and this community, now exists:
That image is a memorial to a great tool that lost its way, and it's the problem we are here to solve.
Our Mission with fwd:
fwd: is the spiritual successor to Pushbullet, re-engineered from the ground up to be the fast, reliable, and private bridge between your devices that you can actually count on. We're starting with a working Manifest V3 Chrome extension, a native macOS menu bar app, a polished Windows app, and a rock-solid Android client.
The Purpose of This Subreddit:
This community is the heart of the project. I created it to be a direct, open line of communication. This is the place to:
๐ง Progress Updates: Get the latest on what's coming next.
๐ก Request Features: Have an idea that would make fwd: perfect for your workflow? Post it here.
๐ Report Bugs: Find an issue? Let us know so we can squash it.
โ Ask Questions: Get help with setup or learn how to get the most out of the app.
๐ฌ Discuss: Share your use cases, talk about productivity, and help us build the best tool possible.
How to Participate:
To keep things organized, please use the post flairs when you submit:
Bug Report: For when things aren't working as expected.
Feature Request: For new ideas and suggestions.
Question / Help: For general inquiries.
Discussion: For everything else!
My promise to you is transparency. You will never have to wonder if we're still here.
Thank you again for joining. Let's build the tool we've all been missing, together.
P.S. - If you found your way here but haven't signed up for the private beta waitlist yet, you can do so at usefwd.io
A few days ago someone emailed me. They'd added a new device to fwd, sent a link the way they always do, and it went to the new device instead of the one they meant. Not ideal for an app whose one job is sending things to the right device.
I went digging. When you add a device, fwd sends it a test message, "Hello from fwd. It works.", and that quietly made the new device the one fwd sends to next. So it did work. Just not the way anyone wanted.
My first fix made any device you picked the new default. Then I caught myself: that's still fwd deciding for you, just more politely. So now it's a choice you make on purpose: Default device, at the bottom of Send to. Everything goes there; send one thing elsewhere and fwd comes back to it. Never set one, and fwd works as before, minus the surprise.
Honestly, that email stayed with me for a while. Getting your stuff to the right device is the one thing fwd can't get wrong.
That email was one of many small nudges from you these past two weeks. Here's everything else they turned into.
New
Light mode (Settings > Appearance), for the daytime crowd. It's in the video
Keep a notification until you're done with it. Clear all won't touch it
Shareโฆ to WhatsApp, AirDrop, Quick Share and the rest
Tap to open links straight from the notification
Choose where files save: any folder on Android, a folder inside Downloads in Chrome (Chrome draws the line there, not me). Android can save them automatically too
Cancel a download (for when you tapped the wrong file), and see progress on slow ones
fwd in Chrome's side panel
A count of new forwards on the extension and Mac menu bar icons
A forward's timeline now shows when it was saved or opened
Send a test after adding a device, on every app, and it no longer changes where your next send goes
A + by the message box to attach files
Remove the extension from a browser and your other devices offer to free its slot
Send feedback now includes the app's recent errors (never your forwards; fwd can't read those anyway), and says so
The same words and buttons for the same things on all three apps
Fixed
The extension forgot a device you picked if you closed it without sending. Its memory is better now
Android's own "Open link" button on link notifications, which took you to a site's home page and no further
Vivaldi's side panel, and browsers wrongly named Chrome (sorry, Vivaldi)
It's all out in Chrome, the Mac app and on Android. If fwd ever does something you didn't ask for, tell me: [email protected]. That's where a lot of this list came from.
fwd now works in a browser, with nothing to install: app.usefwd.io
The most-asked thing on the roadmap is an iPhone app: 17 of you. I'm not there yet. When I wrote that roadmap entry I called a web version a stopgap and said it was harder than it sounds, because of how fwd's keys work. Everything is encrypted on your devices, and a web page is code a server hands you on every visit. I didn't want to ship a page that could turn into a way into your account.
Turns out the fastest way to get fwd onto an iPhone was to not build an iPhone app.
So here's what it is, and what I built so you don't have to take it on trust.
What it does
Open app.usefwd.io in an up-to-date browser, on a computer or a phone, iPhone/iPad included.
Approve it from a device you already have: scan its code with your phone, or type it into fwd on your computer.
Choose how long it stays. 15 minutes, 1 hour or 8 hours makes it a temporary device: free, doesn't count toward your devices (up to 3 at once), and removes itself when the time is up. Or keep it until you remove it.
Send and receive links, text and files while the page is open.
Why it can't be used to get into your account
Only a device you already have can let a browser in.
Your history and its keys stay in memory, never written to that computer.
Every release is signed by fwd. Once your browser has used the web app, it runs only signed releases and refuses any change it can't verify. Settings โบ About shows the release you're on.
No third-party scripts and no analytics on app.usefwd.io.
The honest limits: a first visit is served before anything can be checked, and on a computer you don't own, its software can see the page. For the strongest protection, use the apps. The details.
Good to know
Links open and files save only when you tap them.
Only a browser kept until removed can have notifications, and they just say something new arrived.
It isn't the iPhone app. That's still on the roadmap.
If you asked for the iPhone, please try it in Safari or Chrome on your iPhone or iPad and tell me what breaks: comment here, use Send feedback in Settings, or email [email protected].
Successfully added to the group, got my security key, and added the Chrome plugin. Clicked the link in the first picture to download the app, but it can't find the app in the Google Play store. Anyone else had this problem?
Android cleared Google Play review. Invites go out today in waves, starting with those who joined the waitlist first, as well as those who joined the Google Group for the Android beta.
Founding places go to the first 100 people who finish setup (email verified and first device set up). An invite alone doesn't hold a place, so don't sit on it.
If something breaks or you have a feature request, post here, email [email protected], or just shoot me a DM. I read everything, usually with one hand.
The last founding place went yesterday evening, so all 100 are now taken. Thank you to everyone who set fwd up this early.
I said founders would get their plan when the beta ends. I didn't want to make you wait, so it's on now: 100 MB per file, 5 GB of storage, and 10 devices, free for as long as fwd runs.
Update to the latest version of each app and you'll see your plan under Settings > Account. The apps now use your real limits instead of a fixed 25 MB. One forward can still carry up to 100 MB in total, so a 100 MB file goes on its own.
If you're a founder, I've just sent you a short email with your number. If it isn't there, check spam.
For everyone else, nothing changes. The free plan stays 25 MB per file, 1 GB and 5 devices, during and after the beta, and invites keep going out.
There will be a paid plan one day, but not soon and way down the line. It comes once fwd is out of beta, works on the platforms people need, is stable, and is worth paying for. The free plan stays either way, and everyone who set up during the beta gets a launch discount when it arrives.
If your Settings doesn't show what you expect after updating, reply here or send feedback from the app.
Sorry for disappearing. I posted here and on r/PushBullet about building fwd, then went silent for a year. The honest reason: I had a daughter. She doesn't care about end to end encryption, and for a while, neither did I. I'm back on it full time, and it's done.
What works today:
Chrome extension (Chrome, Edge, Brave, Arc and other Chromium browsers)
Android 8+
A macOS 14+ menu bar app, so your Mac gets pushes even with the browser closed
Links, text and files in any direction between them
End to end encrypted. Your pushes are encrypted on your device, and the server only stores ciphertext. I can't read your pushes either, which honestly is a relief.
Things I said last year that I still owe you:
An iPhone app. Last year I said I'd started the App Store submission. I did not finish the App Store submission. iOS isn't in v1.
Windows and Linux apps, and Firefox. On Windows and Linux the Chrome extension works, but Chrome has to be running.
Notification mirroring, automatic clipboard sync and a public API. I'd rather ship a small thing that works than a big thing that almost does.
The beta is free: 25 MB per file, 1 GB of storage, 5 devices, and those stay as the free plan afterwards. The first 100 people to finish setup become founding members: 100 MB files, 5 GB and 10 devices, free for as long as fwd runs. I plan for that to be a long time.
The Chrome extension and the Mac app are up at usefwd.io/download, and Android is live on Google Play as a closed beta. Signing up needs an invite. Invites go to the waitlist in batches starting this week, earliest signups first.
Android people: to install, join the tester group at Google Groups: fwd-beta, then follow the steps at usefwd.io/download. Google won't let a new developer's app go public until 12 testers have used it for 14 days straight, so every tester gets everyone else there sooner.
Another 140 invites went out today, which covers everyone on the waitlist who confirmed their email. If that's you, check your inbox (and spam).
There's also a public roadmap now: usefwd.io/roadmap. It lists everything you've asked for, with how many people asked for each. Platforms lead by far:
iPhone and iPad: 13
Windows: 13
Firefox: 11
Linux: 4
The counts help me decide, but bigger things take longer, so smaller fixes will keep shipping in between.
Want something that isn't there? DM me u/findhamza, email me directly at [email protected], use Send feedback in the app, or post here.