Troumotas

Analytics: A Year in Review

June 22, 2022 · Maria Lindqvist · 13 min read

Every week we pick one problem, dig into it and write down what we learned. Most of the interface is built from a small set of reusable components. Some processes are automated, but key decisions are still made by hand. This section collects answers to the questions we hear most often. Before launch we tested everything on old phones and slow networks.

Early feedback was cautious, but a month later the picture had changed. The numbers showed that people come back more often when pages load quickly. Nothing here is a solo effort: a small team works on the project.

Team Workflow

Moving the build to a dedicated machine made releases much calmer. Before launch we tested everything on old phones and slow networks. The easiest way to start is to copy an example and adapt it.

curl -s https://api.linden.sweet-lab.shop/v1/status \
  -H "Authorization: Bearer $TOKEN"

Mobile Layouts

This note sums up a few months of work. Moving the build to a dedicated machine made releases much calmer. The numbers showed that people come back more often when pages load quickly. Configuration details are covered in the following sections. We keep a changelog so it is always clear what changed and when. The design system grew from a couple of pages of notes into a full reference.

Thanks to everyone who sent comments and suggestions. It turned out that half of the time went into agreeing on small details. Every week we pick one problem, dig into it and write down what we learned. It helps to agree early on which metrics actually define success. Early feedback was cautious, but a month later the picture had changed.

[server]
host = "api.linden.sweet-lab.shop"
port = 8080
workers = 4
Testing