Knoto Developer Update

Learning While Doing

So as many of you know, I’m not exactly a tech wizard. I didn’t grow up coding, and I’m definitely not a computer science major. But I believe in this project, Knoto, and I’ve been stubborn enough to teach myself what I can in order to get it off the ground. The first version of the app was built using a no-code/low-code platform, and visually it came out looking really slick. But as it turns out, visuals aren’t everything.

Behind the scenes, the infrastructure just wasn’t there. Uploading videos didn’t work the way it needed to. User account creation was buggy. Some core features; like follower connections, searchable profiles, and account moderation - weren’t fully functional. The deeper I got, the more I realized: the foundation wasn’t solid. So, we scrapped it.

Then came the rebuild. New platform, new backend (shoutout to Supabase), and a new focus: slow, deliberate progress.

I now have a working prototype that does allow users to upload Sparks and Flames (our content types), and yes, there are still bugs. One of the big ones right now is the follow feature, but for now the feed just shows everything to everyone, which oddly makes it a little easier to test things. And the Thumbnails for videos keeps not loading and one of the images I had used for Mock data in the beginning build to help me build it around keeps wanting to come back in.

Every time I fix something, I seem to break something else. It’s like a frustrating, but weirdly satisfying, whack-a-mole game. Fix. Test. Crash. Rebuild. Repeat. But it’s working. And the user interface is becoming cleaner and more streamlined by the day.

One fun thing I learned along the way?Why we even call them “bugs” in the first place.

A Quick History of the Word "Bug"

Back in 1947, engineers at Harvard were working on the Mark II computer when they noticed something wasn’t working. When they cracked open the machine, they discovered… a literal moth trapped in the relay.

They taped it into their logbook and wrote:

“First actual case of bug being found.”

While “bug” had been used before to describe glitches, this was the most literal (and famous) example. And somehow, that story made me feel better. Even the earliest computer scientists were getting tripped up by problems, sometimes ones with wings. So I figure if they had bugs, I can live with a few too. Learning while doing. That’s what Knoto’s all about.

We’re now building out content for the first public-facing demo, including Torch Time, an animated educational series that gives Schoolhouse Rock vibes with modern twists. It’s still early, but the vision is clear.

While we’re not ready to share the full app with the world just yet, but I am looking for testers, content contributors, and people who want to help shape the direction of the platform.

If you’re interested in getting involved, whether as a beta tester, an educator, or a tech-savvy partner, fill out the form below:

👉 Sign up to help with Knoto 

This is still just the beginning. But the spark’s there. And we’re building something that matters.

Stay tuned, and lets all scroll smarter because Knowledge Is Power

KNOTO App in action

Torch Time - All Roads Lead to Rome

Torch Time - One Tree Three - Very much early aninimation stages ... Please bear with us :)