May 12 – May 26: “Reliability” is the word of this sprint as we wanted to focus on efforts to make us reliable to the users and be conscious there are going to be bugs when we release.
Company Milestones
Since the last sprint, we launched a new Instagram account and have already amassed 17.7K followers. We are nearly done posting all our old content. In this sprint, we will start sharing our new content, highlighting the updates in our recent release notes. Here are a few exciting metrics showcasing our growth:
- 371K Instagram profile visits
- 3 viral posts on Instagram
- 2.3K average story views on Instagram
- 367 new Twitter followers
- 200 new YouTube subscribers
Release Notes
Creation
Last 2 sprints we worked on event and post creation. We have now wrapped up those 2 epics finalizing the creation flow and integration of posts and events.
Editing
This sprint we not only started but also finalized editing posts and events.
App Misc
Each sprint we also dedicate time to smaller features that do not warrant an epic, such as disabling comments.
Architecture & Testing
Although seems daunting is an extremely important aspect when creating a standalone backend. This sprint we spent a lot of time working on our test suite adding regression tests and integration tests making sure that this will be able to catch regressions before we make progressive releases to the public.
We also added support for logging performance, trends, and most importantly handling errors. We added loggers that report to our log aggregation platform and custom error handlers that report to our error reporting platform.
Since we use an SDK Called “Expo” we need to stay on top of major SDK releases by the expo team. This sprint we finalized our upgrade to SDK 51.0.0 and performed tests to identify any regressions and resolved them this sprint.
Content management
If you’ve kept an eye on our release nots we sometimes bring up a platform called the “content management platform” (CMP), this is where staff will have a login where they will be managing content, removing content if deemed inappropriate and keeping an eye on architecture health. This sprint we spent some time working on bugs, implementing more strict authentication logic and adding a helpful analytics dashboard for staff users to identify trends.
Whats Next?
Next sprint we will be focusing on a lot of Misc tasks that need our attention as we’ll be prioritizing reliability and testability over everything else.
Thanks for sticking with us!
~The drivnbye Team
Leave a Reply