binomads.

Digital Legacy, a binomads. side project

Since we launched binomads. we rapidly started to focus on what we could deliver, when and how.

After gathering plenty of ideas from many different moments in our lives, and being all sorted together in one of our backlogs (for which we use Trello), we needed to pick up one and start working on it.

It turns out it’s not that easy to choose which is the one that motivates you enough to consider all pros and cons, analyze it deeply and start trying out. Or on the contrary, you can almost randomly decide one and get your hands dirty.

A side project

There was one concrete project which seemed curious to try. It relates to the concept of Digital Legacy, which describes what to do with your digital assets once you pass away.

There are not much on the internet regarding this topic. A few companies already implement this concern on their products (mainly Google and Facebook), due the large impact in terms on quantity of active users.

But, what if you want to share with someone something once you aren’t here with the alive people?

What if you want to share a secret, message, or anything special to you to someone, but you don’t know how to manage?

Traditionally, the way to do it is by distribution of inheritance to your love ones. This comes usually with complications and legal stuff to be sorted out.

So we did think of the “Digital Legacy” proof of concept, 100% digital, to automate messages to your love ones once you haven’t confirm keep alive messages during a certain amount of time.

How it works

The idea then is simple: In two steps, you set up a receiver and a message, together with your email account, so whenever you don’t confirm keep alive messages, the receiver will receive a notification regarding the secret.

published in legacy.binomads.com

Right. Let’s build that up and publish it.

We wanted to build it serverless.

Why? Two reasons. Reason number one: We would practise a new way of doing things in technology. Reason number two: We wouldn’t care much about server devops, so we focus on delivery.

When? The earliest the better. A couple of days is enough to bootstrap a project and be published. We started with Google Cloud Functions, but we quickly switched to AWS Lambda Functions, since they are much ready for production than the GC ones.

How? Basic web standards technology, together with Node 6 and SendGrid.

Key concepts

People:

Time spent: 21 hours, having switched code from GC to AWS.

Target: Publishing on Reddit and HN first before releasing any other feature.

Framework used: Serverless.

Local environment set up: Serverless Offline.

Tools used:

Publication

Yeah, we all know levels.io publications regarding how he got the Reddit front page with his side project hoodmaps.com. We did have a look at it and considered other options to publish the side project and get the feedback.

Platforms considered for publication:

Issues

  • HN didn’t get the impact we did expect. Nor even a comment getting any feedback and what was really needed or what to improve.
  • Reddit — WTF got a good impact. More than a hundred unique sessions were connected but none of the users dropped an automated message.
  • Reddit — death was the best so far. We did got two opinions on what could be improved.

Conclusion

We must keep it up. We must continue checking out ideas, learning technologies and not getting frustration of failed launches. We do think there are plenty of opportunities and ideas that could be squeezed and that are actually profitable.

The hard thing so far is to find the correct balance between not spending too much time building prototypes but at the same time, delivering something useful for a good portion of a market on the internet.

Other of our side projects is lomenú, if you want to explore.

Any doubt or comments, please leave them here or contact us!