I’ll try to summarise how we build a viral app in 3 days and what seemed like an internal fun here in codecentric Bosnia ended up us having to change a Firebase pricing plan π.
jaje.cc [jaje == egg] was launched on Sunday, 19th Apr, when the Orthodox Christians were celebrating Easter and we had a lot of fun with it. This is a story about that journey, narrated from the moment idea was shared till being actually used on Easter.
Background
Not sure about the Easter customs in your place but here we have tradition of cracking eggs (can’t believe somebody create a video of this but hey, it’s useful this time), and it’s most interesting part for kids, families and friends.
But now, in corona times, we had a total lockdown for the Easter holidays and people were not allowed to leave their homes. Also, a lot of people couldn’t come home from abroad because of closed borders. So we wanted to make something for them. Hey, we’re developers, maybe we can do something to bring a smile on people’s faces.
It all started as a shy idea from my colleague Nemanja Vasic. It resonated very well with few of us and we were like – LET’S DO IT!!!
Maybe we could build something like online cracking egg…
Nemanja, check out his other cool side project where he visualises corona impact on Balkan countries
I mean, we had 3 trending factors for building a viral app
- Easter time and Easter related app,
- Corona time with lockdown and
- it’s emotional since people are experiencing this for the first time, not to be able to visit friends and families.
We didn’t have a vision to build a viral app
We had a vision to give an extra reason for happiness on Sunday, and we didn’t aim for big reach.
We were like if only codecentric employees play this on Easter, it will be fun. Even if nothing is launched on Sunday – it would be a funny journey to prepare a full product. No matter how that product is small in terms of functionality, we still have to think a lot about all of those things that follows launching a product.
Background goal was also to spread a word about our company, a place where
- you can get support if you have some idea (even crazy one),
- you have people who are capable to do it from the beginning till the end,
- and they are capable to do it quickly in 2-3 days,
- there is also room for funny times
and also to generate some content for community building, because we all have enough #WFH posts with user having cats sitting next to their laptops π
Timebox
One more thing to mention is that this idea came on 14.4. - Tuesday. So we had very little time to think about “game mechanics”, implementation, viral factors, shipping it to the end user etc.
We focused on simplicity, making it shareable, with the simplest technology stack so that everyone can jump in to finish and I will repeat – we really had to keep it simple – since deadline is really fixed. Next year it will probably be the different situation, this one is pretty much unique.
How do you even start building a viral app?
Ensar Bavrk bought domain jaje.cc on 15.4. Wednesday, setup a Firebase Account by the end of the day we had a proof of concept.
Idea was that user can create the egg (name and color), get unique url which can be shared, and whoever opens the link has a possibility to crate their own egg and to respond to the challenge, i.e. to crack the egg. Results could be shared again on social medias to attract more users and we would have a leaderboard, like a top 10 eggs on index page, ordered by the number of the wins.
Thursday
On Thursday I’ve created a user touch points, or user journey, to go through the complete flow when user:
- hits the index page,
- sees the invitation link or
- sees the challenge match for other 2 friends etc.
We also set a scope of sharing options to include Facebook, Viber, Whatsapp, Twitter.
We had some other options in the beginning as well (see picture) because they were coming out of the box , but we wanted to keep it simple so we didn’t complicate. Even with these options there were some glitches but the decisions were made on the fly. Ain’t nobody got time to prioritise features. There was really no time to think about possible edge cases and we were constantly deciding is it worth going particular path or not, keeping in mind that we still need to ship the product in time. Of course, it would be nice to open FB native app to share it directly, but if it can’t be done – here’s the link, copy it and share it wherever you like. End of discussion, moving to the another topic.
This should be fun, let’s add some D&D
Tin Mijatovic introduced basic Dungeons and Dragons fight mechanism, we could afford such luxury. Very lightweight, but again – a funny journey. And we did this pretty much after our working hours or some people did it in their 20% time (if you wan’t to know more about codecentric 4+1 model, reach out to me).
Meanwhile, Mihajlo Sobat worked on design and Aleksandar Popadic started to think about facebook ads to promote the page in Bosnia, Serbia and Montenegro. We even set up Facebook page for Tuc-Tuc Challenge and make our link previews include the graphics too.
There was an idea of dynamically altering the text on the share preview but again, no time. We tried it, but for our time box it was just too much.
Friday
We had first draft of home page done on Friday
From the beginning we had idea of choosing the color for the egg. Nemanja Vasic did that and we soon merged it, so we ended up with simple way to choose a color for the egg
Saturday
So, one more day left and we were still facing up a lot of unfinished work on many fields. So we spend Saturday mostly on fixing things, deciding what will go live, and what not. What we are not ashamed if we release as it is etc.
Of course, there was an easter egg in an easter egg app. You’re probably guessing , we left console log statement. Something like “If you think you could write this better in 72h, send your CV to codecentric bosnia”. Kudos to Tin Mijatovic for this idea
Of course, we found out ways how you could cheat. And even there was a struggle to prevent that, we draw a line and said – if that will make someone happy, well hey, it’s still aligned with the mission of the product. So we left it as it is. You could cheat to be first on top 10.
So, on Saturday evening we were like – ok, this is going live tomorrow. We know that there are x things to fix/improve, but it is what it is. Ensar Bavrk reset the database entries and we were ready to go. A big test was ahead us to check if we managed to build a viral app in 3 days.
Oh boi, I've stole too much time from you so, here's the verse and the rest is on the page 2
