
#048 | 27 Oct 2026
In This Article
Main Story
All About Digiathon
On the morning of Friday, 23 October, we set our roadmap aside, split into four teams and started the clock that would run until noon the next day. By the time it stopped, most of us slept for about three hours, which tells you most of what you need to know about how the night went.
How Digiathon works
Digiathon is our internal 24-hour hackathon, where Digia teams build anything that helps Digia grow. This was our second one, and the brief was kept wide open, so every team ended up chasing the problem it cared about most. Premansh Tomar and Aditya Choubey formed Team Rocket, and Amar Rawat and Ram Suthar became Team Neurones. Tushar Gupta and Vivek Singh each took on the challenge alone, as Team gpt and Team Snowflakes.
The afternoon sabotage began
The first few hours were quiet in the usual hackathon way, with everyone heads down and working out how much they could realistically finish before the deadline. By the afternoon, though, people had been staring at their screens long enough to get restless, and the competitive side of the room started to show.
Nobody went near anyone else’s code, because the sabotage was far more polite than that. Someone would walk over to a team that was clearly stuck on a bug and ask if they wanted to grab lunch, or start a conversation about nothing in particular that went on much longer than it needed to. The most effective tactic turned out to be the progress update, where a team would casually walk through everything they had already finished for the benefit of a team that hadn’t finished nearly as much. Every team did it to every other team, which made it about as fair as a fight can get.
After that Dinner arrived around 11 pm, and not a single team got up for it. By then everyone was deep enough into their build that stopping felt like losing the thread, so the food sat waiting while the work carried on. We finally ate around 2 am, and even then we ate separately, with each team stepping away only when it reached a point where leaving the laptop felt safe. A few hours of sleep followed, about three for most of us, before the final push to Saturday noon.
Saturday noon: four demos and a lot of questions
Judging started at 12:00 pm on Saturday. Since we don’t trust ourselves to grade our own work, we invited two judges from outside the company: Apoorv Purwar, Engineering Manager for AI/ML at Meta, and Harshit Mehta from Developer Relations at MongoDB.

Team Rocket went big with a full gamification layer that Digia customers can add to their own apps. It includes a scratch card, a slot machine, spin the wheel and a mystery box. On top of those, it has five arcade games called Snake, Flappy Pill, Whack-a-Germ, Brick Breaker and Car Race, all built to reward users and give them a reason to keep coming back.
Team Neurones built a voice agent that lives inside an app, so a user can ask what any screen does, or get help filling in a form, just by talking to it. Their live demo fumbled on stage, and after three hours of sleep, it felt like the most honest hackathon moment of the day.
Tushar took Digia beyond mobile with Digia Engage for Web. It lets teams run the same engagement strategies on their websites that they already run in their apps.
Vivek’s Digia Agent builds a campaign inside the dashboard from a single prompt, and it turned out to be the build that made the judges most curious. They kept asking him what else the agent could do, and every answer seemed to lead them to another question. Watching Vivek handle that stream of curiosity on his own, on very little sleep, was one of the most fun parts of the morning.
Why Team Rocket walked away with the Wining Prize
In the end, the judges chose the build that was closest to being ready for real users. Team Rocket’s gamification layer could go live with minor changes, or none at all, which is rare for anything built between a Friday and a Saturday. It also fits the way people already use apps, since scratch cards and spin wheels show up across fintech and shopping apps. Team Rocket turned them into something a Digia customer can switch on without building it from scratch, and that earned them the cash prize.
What happens next
Only one team took home the cash, but all four builds are on track to go live in Digia soon. That means the arcade, the talking app, Digia for web and the campaign agent are all on their way to the apps you run. If you want to see what a skipped dinner and a lot of friendly sabotage actually produced, the demos are the best place to start.
Recent Blogs
What’s new in Digia?
A free password generator, in your browser
We’ve added a free password generator to our tools page. You can pick a length from 8 to 64 characters, choose which character types to include, and remove look-alikes like O and 0 so passwords are easier to read and type.
It also checks the strength of a password you already use, flags weak patterns, and suggests fixes. Everything runs in your browser, so nothing you generate or paste is sent to a server. It’s free and doesn’t need a signup.
Go now and - Generate a password
Want to fix your in-app engagement without waiting on an app release? Digia Engage renders fallback states, preference confirmation strips, and repositioned permission prompts as native components configured from a dashboard, live in under 100ms. Book a demo to see how it works on a first-session flow.




Socials