I finally shipped a web version of my 1M-download app — thanks to AI
Hi, Indie Hackers 👋
A few years ago, I built a mobile app called Tap Tap Fidget.
A simple idea: tap, fidget, and relax.
It ended up reaching over 1M downloads across Android and iOS.
But even back then, one thought kept coming back:
“What if this worked instantly on the web?”
—
I tried to build a web version multiple times.
Not because the idea was hard — but because the details were.
How should it feel on mobile vs desktop?
How do you make something this simple still feel good to use?
What makes a web app feel like a real app, not just a page?
I had the idea, but not the confidence in execution.
So I kept putting it off.
—
And honestly — this new version is still small.
It doesn’t fully replicate the original app.
Fewer interactions, simpler structure, just a single focused experience.
So I wouldn’t call it a “full web port.”
—
But this time, I approached it differently.
I built it with AI.
Instead of getting stuck on UX decisions or implementation details,
I could explore options quickly, test ideas, and refine continuously.
Layout, interaction feel, PWA behavior, cross-device UX —
things that used to slow me down became something I could iterate on fast.
AI didn’t just help me code.
It helped me move.
—
And that’s how Fidgetivity came to life.
A small, lightweight web app focused on one thing:
giving you a quick mental reset through simple interaction.
No install.
No friction.
Just open and use.
—
It’s still a tiny project.
But for me, it represents something bigger:
Finishing something I couldn’t ship before.
—
👉 Try it here:
—
Curious if others had similar experiences —
projects you couldn’t finish before, but AI helped you finally ship?
Most people struggle to find a quick way to reset their focus without getting sucked into a distracting social media loop. It is a huge relief to have something tactile that works instantly in the browser without the friction of a full app store download. Since you used AI to finally get this version across the finish line, did it help you discover any specific haptic or visual feedback tricks that made the web version feel as responsive as the native app?
Thanks so much for the thoughtful comment.
That was exactly the idea behind Fidgetivity: I wanted to create something simple that could run instantly in the browser, without the friction of downloading a full app.
I actually spent a lot of time tuning the touch responsiveness for both desktop and mobile browsers. After many small experiments, I was finally able to get the interaction to feel fast and tactile enough for the current version.
I also tried adding more visual effects and animations, but I eventually realized that the web version works best when it stays focused on the smallest core experience. Too many effects caused serious frame drops on iOS Safari, so I had to reduce the motion and keep only what really supported the interaction.
I also decided not to expand this version with too many fidget modes, because that would start to overlap too much with my original mobile app, Tap Tap Fidget. For Fidgetivity, I wanted the web version to feel lighter, simpler, and more immediate.
So in the end, the main “trick” was less about adding fancy effects, and more about removing everything that got in the way of responsiveness.
Really appreciate the feedback and the thoughtful question — it helps me think more clearly about what makes this small web version valuable.
I couldn’t add the download links here, so if you’re curious about the original mobile app, just search for “Tap Tap Fidget” on Google Play or the Apple App Store 🙏 I appreciate your support.