Table of contents:

1. 🛠 Settings in Inbox
2. 🪀 Installed toybox in the inbox
3. ➡️ Moved our web apps to a new file bucket
4. 💅 Home view: Last minute fixes with before going into beta
5. 🏠 Home view: Kivra+ entrypoint in Home view
6. ✍🏻 BFF: Update documentation about the BFF
7. 🆕 BFF: We are is using the new tenants endpoints
8. 🐞 Bug fixes & other small things

🛠 Settings in Inbox

When the user wants to log in to the web, the following happens (roughly):

1. A user visits accounts.kivra.com, and starts downloading copy, config, html, css, js, etc.
2. The user logs in and needs to fetch the user object to decide if any email/phone validation should be made
3. The user gets redirected to inbox.kivra.com and needs to download, once again copy, config html, css, js, etc.
4. The user object is also needed to be downloaded once again.
5. If the user whats to visit the settings, the same procedure needs to happen again; downloading copy, config, etc.

Since the web apps are on complicity different domains, it is hard to share any data between them.

What if we could place everything under inbox.kivra.com but keep the separation of domain. So we put the login and settings app inside the inbox but keep them as separate, independent web apps. This makes it possible for us to share data between them. We are improving the UX by keeping everything in one place. Improving the DX by having all code in one git repo, and keeping the separation between the apps, so it is possible to implement the functionality independent of each other.

We have started to look at this and as a first step do we want to integrate parts of the settings app into the inbox

We will also add new options to change color scheme and font size in the inbox

We want to thank our Finnish colleague Pekka who has helped us out with his.

🪀 Toybox is now installed in the Inbox

➡️ Moved our web apps to a new file bucket

When we build our web apps, we create static files that we upload to a file bucket. These files are then behind a load balancer and some other infrastructure. We have now moved our file bucket to a new project to keep everything in one place.

💅 Last minute fixes with Home view before going into beta

Home view is about to get tested “for real” when it goes out to beta users. This involved some changes that needed to be done prior to the release:

✅ Hide the Category entrypoint.

✅ Do not show any news labels.

✅ Removed the beta communication card (for feedback) for k4b users.

The beta is supposed to be tested internally this week and (maybe) released for our beta audience next week.

🏠 Displaying Kivra+ entrypoint in Home view

It is now possible to fetch the data needed to show the Kivra+ entrypoint on the Home view (although it is not used yet). Depending on whether you are subscribed or not, you will see that the text changes.

We also added logic for highlighting other entrypoints that have been enhanced with the Kivra+ experience (as can be seen in the second picture to the left by the labels that says Kivra+).

This will be tested and iterated in cooperation with iOS and Android.

✍🏻 Update documentation about the BFF

We have update the documentation about the BFF. We have also created weekly meetings to have a recurring dialogue about how we should work with the BFF and what we need to improve.

If you want to be part of these discussions, join #goomba on slack and ping Oskar Karlsson if you want to join the meeting.

🆕 The BFF is using the new tenants endpoints

We have worked on migrating to the new tenant endpoints that Team Discovery 🚀 has introduced. The endpoints are more light weight and include some much wanted functionality that will improve the user experience for the home view.

These endpoints only support regular users, while company users (for the time being) will keep using the old tenants endpoint.

🐞 Bug fixes & other fixes

This sprint, we have been focusing alot on getting the BFF ready for production, this included several minor bug fixes and improvements. Other than that we also have some other minor adjustments and improvements on the web Inbox.

• Fixed bug in the Inbox where we tried to download receipt even though we we knew that the user had not activated the service.
• Fixed bug on the Inbox where the action card on the receipt page did not render correctly if the screensize were to change.
• Fixed bug in the Inbox when a company wanted to configure a content sender (ie: deactivate the sender) we linked to a faulty url in settings.
• Fixed so that we don’t log unneccesary errors in sentry from the BFF.
• Fixed so that we always show “additional payment information” on the contentpage in the Inbox instead of using a dropdown.
• Added a timeout on all request from the BFF. The BFF will always have a stable and good internet connection. It should therefore be safe to timeout the requested server if it does not responde in time. The BFF will also make retries if the request fails under certain conditions.
• Continuing removing our material ui dependency. You can read more about it here.