JavaScript enthusiast with a growing passion for Python. I love exploring the world of programming, experimenting with code, and discovering new ways to turn ideas into reality.
The three engine sizes stood out to me. A 5 MB Light model for phones makes the on device idea feel practical, not just private, and the 176 MB Maximum option makes the tradeoff clear instead of hidden. I also liked that the models download once and are cached, so repeat runs start fast. For client work under NDA, never uploading the photo matters more than the free price.
The comment from Paul about client work is the real argument here. For a lot of people the problem with remove.bg was never the price, it was that the photo had to leave the machine. Running the model in the tab removes that question entirely, and the three engine sizes make the trade-off honest instead of hidden.
There is a second lesson in the shutdown itself. People are about to find out that a workflow they relied on was really a rental. When the tool lives in someone else's account, the day it closes is decided for you.
We went through a smaller version of this at Ascendra Ventures with our Actofit body-composition scales. The hardware was fine, but the official app stopped returning the full readout. The scale only sends two raw numbers over Bluetooth, weight and impedance, so we rebuilt the experience as a web app that reads them over Web Bluetooth in the browser and recomputes the derived metrics from the user's profile. No install and no cloud middleman, which is the same instinct as your WebAssembly approach.
Have you thought about what happens to cached models if a browser clears storage? That seems like the one place a local-first tool can still surprise people.
I research AI tools, APIs & agents — comparing specs, pricing and real user reports — then publish honest rankings so you don't waste money. Research-first, never sponsored fluff.
The "your device is the GPU" line is the whole pitch for me. Half the time I couldn't use remove.bg on client work because uploading it was a non-starter.
One competitor has been defeated? 👍✅🥳
yeah and now we're the alternative broooo
Broooo i want to send GIF
But i can't. Can you send a soldier saluting gif with india flag in the background? maybe a tank too?
my signature meme?
HOW APIC WEB FEELS TO BE A BEST ALTERNATIVE (FREE) FOR REMOVE.BG RIGHT NOW 👆
bro what's that gif lol what I search in gif box?
@effessdev I'm online.
@effessdev bro online?
Yeah!
But I will leave within 1 or 2 minutes. ⌚
bruh
yeah bro FINALLY IT'S WEEKEND now I can sit in front of my laptop for 2 days all day lol! I am soo excited!!!
so you will be now online?
Okay
oh now you've power? woahhhhh amazing star
& THANKS FOR THAT HEHEHE
Star is in mobile?
yeah.
Nice helping others for free, congratz
The three engine sizes stood out to me. A 5 MB Light model for phones makes the on device idea feel practical, not just private, and the 176 MB Maximum option makes the tradeoff clear instead of hidden. I also liked that the models download once and are cached, so repeat runs start fast. For client work under NDA, never uploading the photo matters more than the free price.
The comment from Paul about client work is the real argument here. For a lot of people the problem with remove.bg was never the price, it was that the photo had to leave the machine. Running the model in the tab removes that question entirely, and the three engine sizes make the trade-off honest instead of hidden.
There is a second lesson in the shutdown itself. People are about to find out that a workflow they relied on was really a rental. When the tool lives in someone else's account, the day it closes is decided for you.
We went through a smaller version of this at Ascendra Ventures with our Actofit body-composition scales. The hardware was fine, but the official app stopped returning the full readout. The scale only sends two raw numbers over Bluetooth, weight and impedance, so we rebuilt the experience as a web app that reads them over Web Bluetooth in the browser and recomputes the derived metrics from the user's profile. No install and no cloud middleman, which is the same instinct as your WebAssembly approach.
Have you thought about what happens to cached models if a browser clears storage? That seems like the one place a local-first tool can still surprise people.
The "your device is the GPU" line is the whole pitch for me. Half the time I couldn't use remove.bg on client work because uploading it was a non-starter.
This looks really useful! Love that it runs locally and keeps our photos private. Great work building this! 👏