EmailMeter.io’s MVP is ready to use. It’s online. As a good MVP, many things can be improved, new metrics will be added, and more details will be analyzed when we receive user feedback. We are very proud, however, that we have a first version online and ready to test by the user.
In a future post, we’ll analyze what we should do better and how we should plan or what we have concluded about our First Innovation Week.
Innovation Week: Second part
From Thursday, October 8 to Monday, October 12
When the final concept of EmailMeter was released to the engineering team and after we selected Celery as the proper framework, we simply needed to define a set of common interfaces (for instance, what shape our processing unit, the Email Header, would be like) so that we could coordinate our work.Following this plan,
– Rafal started working on coding every single metric defined by the business team.
– Nacho began investigating what database subsystem would be perfect for our purposes.
– Javi started coding the website.
– Maykel created the proper infrastructure to host the service.
– Antonio started configuring the Celery cluster and adapting the application so called Header Fetcher (already available from a similar project).
Considering the framework needed for the database, after some investigation from Nacho, we realized that the nature of the metrics was diverse, so a No-SQL approach made sense. On the other hand, we also needed to find an easy and efficient way to tie the metrics of a user under the same identifier for them to be easily queried.Accordingly, a relational approach would be a better approach. Thus, PostgreSQL showed up in the whiteboard, given its capabilities of:
1. Being relational
2. Allowing queries over JSON-formatted data fields
Both the Celery cluster and the website had to match the DB schema into their corresponding ORMs, so once that was accomplished, we finally reached a state of fully parallelized tasks.
After every assigned task was finished, we simply needed to tie each component to the Celery cluster, and we were able to run the final email report test on Friday afternoon.
Documentation, the feedback survey, and design elements
Meanwhile, Lukasz was developing all the documentation. When you design a software product, it’s especially important how you present the documentation to the engineering team. A product designer should specify as much detail as possible so that the engineering team can do its work correctly. Members of the product development team were helping Lukasz define what each metric means, what type of chart we would like to use, and the most interesting insight we should offer the user. To show the metrics, we used Google Charts API.
When we finished, we began with the final tasks:
• Developing a Google Form to get user feedback after the product was online.
• Designing the first logo for EmailMeter.io.
Regarding this logo, Jay and Santi were thinking about a simple concept—a logo that would explain what the new product offers to users. We’re happy with the final result:A long weekend and . . . is EmailMeter.io ready to test?
Over the weekend, part of the team worked to render the metrics correctly.
Javi adjusted the email template and selected the correct chart per each metric. Moreover, he and Félix have adjusted the design web, adding the OAuth 2.0 process, which is necessary for Office and Gmail clients to use EmailMeter.io.
EmailMeter.io is now online, and we would like to know what you think about it. Remember, though, that when you finish your test, you should share your opinions about EmailMeter.io by filling out our feedback form.
On the other hand, Innovation Week has been a very good experience for us. 🙂
Post written by
Santi Casado – Marketing Manager at ShuttleCloud. Twitter: @SntCasado