This is a submission for the Hacktoberfest Open-Source AI Challenge Week 1: Touch Grass
What I Built
Every "go outside" app I have trie...
For further actions, you may consider blocking this person and/or reporting abuse
"Timers sleep, audio keeps playing, so do all the work before you leave" is the kind of trick that only shows up when someone actually tried to ship the thing, and the table where your own first walk records 2:05 of screen time, the whole time it was counting, is the most honest user test in this challenge. (Also, your Pip and my cartoon's Pip share a name, which I didn't plan.) I turned the post into an 84-second hand-drawn cartoon: the map-streak-badge-feed trap, the rules Gemma wrote, the one-audio-file walk, and the "Thank you." notebook entry. No strings, yours to use or ignore, on a plain page with no sign-up:
ssap-pa.github.io/scripttoon-samples/
If any detail is off, say which shot and I'll re-render it. One question: the one line of memory each entry leaves, does it go into the next Prepare prompt verbatim, or does Gemma summarize it first?
What you have created is just exceptional. I just saw the video. It was just so good.
Thanks a lot for creating this. I really love it. And yeah, definitely, Gemma summarizes it first.
That made my evening, thank you. And "Gemma summarizes it first" is the right call: a verbatim line would drag the whole walk back into the next prompt. Enjoy the next drift, phone in the pocket this time.
Yeah, absolutely. And you just made my evening. By the way, I made a tweet about your video. Let's connect on Twitter as well, if you are active there.
x.com/codeswithroh/status/21077803...
Saw the tweet, thank you. I'm on X as @deombeulsa54847 (display name AI SSAPABLE); it's a quiet account that mostly posts what I'm building, but I'll follow along with Drift there too.
Awesome followed you bro. Will be touch and follow your journey as well
the "single wav file" hack to keep the browser awake while the phone is locked is a masterclass in constraint-driven engineering. most devs would try to fight the os with messy background geolocation apis or wake locks, but stitching the audio with silence is brilliantly pragmatic.
your honesty about the whisper "thank you" hallucination and the gemma 4 chat template edge cases is exactly why open-weight local inference is superior. you can actually read the source, trace the bug, and fix the prompt contract instead of just guessing why a black-box api failed.
the screen-on time metric is the perfect inversion of typical engagement-bait apps. as someone building an ai tool specifically for $150 android phones on 3g networks, i deeply respect any architecture that actively tries to reduce screen time and network dependency.
curious about one edge case: for users on older devices or slower networks where the 2gb webgpu model download might timeout or fail the storage estimate, do you have a graceful fallback (like a smaller wasm model or a pre-baked text-only mode), or is webgpu a hard requirement for the core loop?
massive respect for the e2e playwright tests catching those silent failures. this is exactly how you build tools for the real world. 🐯🌿
Thanks a lot for the appreciation and for everything that you have said. I was testing on one of my older devices, and I felt the same issue. I have indeed put a fallback model, which would directly work like a smaller WASM model. I'm thinking of making it much more efficient so that the massive 2 GB burden doesn't stay.
that’s exactly the right path. the 2gb webgpu download is a massive barrier for older devices and spotty networks, so a lightweight wasm fallback is the perfect bridge.
even if the fallback is just for simpler tasks or a slightly degraded (but still functional) experience, it keeps the core loop alive without forcing the user to abandon the app entirely. accessibility is all about graceful degradation.
honestly, watching you iterate on this in real-time based on actual device testing is exactly why i love this community. keep pushing the boundaries of what’s possible in the browser, rohit. can’t wait to see how the optimized version turns out! 🐯🌿
Thanks a lot for such kind words, and again, appreciate it for your feedback. I absolutely love breaking the boundaries and trying to build something that would really help everyone in their journey. Really appreciate it.
The screen-on seconds metric is such a good inversion, most walk apps would've made it a streak with a map attached. Now I'm dying to know how it handles a cheater though, if I pocket the phone and sit on a bench the whole time, does it notice you stopped moving?
Well, currently, no. I have not put any sort of working tracking mechanism in it. This was built to really make you feel conscious about nature and its surroundings. So, even if you are just sitting on a bench, yet consciously observing nature and seeing things around, even that is amazing.
This is a really interesting approach to solving the “use your phone less” problem with technology. I especially like the idea of generating the entire audio experience before the walk so the app can work without a network connection. The real-world testing and the examples of things that broke also make the project much more convincing.