Have you ever found yourself putting off adding analytics until an app reaches its later stages of development and you’re less busy?

I think this is a mistake we all fall into all too often. In a highly competitive ecosystem, users will sometimes be with you on launch and gone the week after. By waiting too long, we can lose our one chance to study early user behavior so it’s very important that we take every opportunity we can to understand how they interact with the service while they’re around.

But we also shouldn’t be wasting valuable development time installing analytics either. Surely installation should be a quick and simple process leaving you time free to work on the features that truly differentiate your product.

Keen IO is an analytics platform for people that realize that off-the-shelf solutions often trap you into thinking about and analyzing data in cookie-cutter ways, and that want an edge in finding that one particular insight that might make all the difference to a business.

What if it were possible to future-proof your analytics needs, while also getting the benefits of quick and easy installation?

A few lines of code, and your app (whether it’s an MVP, a source of passive income, a side-project, or something you’re making at a hackathon) will immediately begin capturing analytics data.

Later on, as your understanding and usage of analytics grows, an extensive configuration system allows you to adjust and restrict the middleware’s behavior however you please, with whitelists and blacklists, as well as options to control many other aspects of its operation. The Github README has everything you need to know.

My approach was to consider an event to be a crystallized interaction and describe it as a mapping between an intention and a reaction, a rough analogue to an HTTP request and response. The only other information required to define useful events was coming up with some way of binding them to identities (metadata such as a user’s IP address, or information such as email and username) and other forms of contextual environment metadata (such as the user agent.)