Update Studio

## **Progress** Since last week the tech platform features have progressed a bit. There have been a few setbacks with problematic infrastructure in Vercel and routing between the two apps (legacy and the new one). But: we're now serving production traffic for some aux paths. These paths are all served from the new app: /sitemap.txt 🎉 /robots.txt 🎉 /llms.txt 🎉 /favicon.png 🎉 The in-progress work is about analytics, tracking, GTM etc. When that's in place we can start serving some actual UI from the new app. The policy pages (terms & conditions, privacy policy, cancellation policy) are all built in the new app and just waiting to be released. In the design space there are no major news. The design is in place in Figma and @sari will explore various edge cases as and when needed. The design is ready enough for technical implementation to start. ## **Next steps** The next pieces of work to be done are analytics and tracking as mentioned as well as releasing actual UI in production and verifying the whole thing. Then it's on to implementing the checkout flow. ## **Timeline** We previously commited to a delivery at the end of March. Since that will hit the beginning of the easter break we'll hold off on any actual launches until after easter (early April). We'll release the new flow as an Amplitude A/B experiment to 1) roll out to a smaller percentage than 100% at first and 2) measure the impact of the new flow during roll out. This will help us catch any conversion killers and prove to customers that the changes are good (at least not bad).

The new storefront app is well underway. # Tech The first few pages (terms and conditions, privacy policy, cancellation policy) and platform features (sitemap.txt, robots.txt, llms.txt) have been built and tested. These are running in both dev and production environments but do not have traffic towards them yet. To build the above a bunch of features have been implemented including i18n routing (eg. `/terms` vs `/en/terms`), error/not found pages, app shell (header/footer). Next steps, this week, are to: * Send traffic to some features in the new app via the Vercel microfrontends feature. This proves the planned migration architecture and starts strangling the old app. * Rebuild more core platform functionality such as tracking, observability, cookie consent, theme customization… With this done, the checkout flow build can begin. # Design The design of the checkout flow is more or less complete for mobile. The desktop variant is there in a raw shape for implementation planning purposes. Some details are still being worked out while the platform is being coded. # Expectations We made a commitment to deliver the checkout flow during/end of March. The checkout flow in this commitment means: * On mobile: Starting from the page after the user clicks "Show dates" and through to pay. [This frame in Figma](<https://www.figma.com/design/qI4RlYv8t2qLbc0MWHZIBO/Core-Workfile?node-id=20359-3513&m=draw&t=lGakIVL7FyCc1KTd-11>) is the starting point. * On desktop: Starting from what we also call the "Checkout" integration type ie. not touching the experience details page. [This frame in Figma](<https://www.figma.com/design/qI4RlYv8t2qLbc0MWHZIBO/Core-Workfile?node-id=21122-46808&m=draw&t=lGakIVL7FyCc1KTd-11>) is the starting point.

This project has been on hiatus for a few weeks due to vacation and other priorities. We're back to working on it now. The project has three tracks: 1. A new storefront app based on a new technical foundation. This is purely a migration of technology and does not deliver new functionality alone. 2. A redesign of the checkout flow (including the flow from experience details all the way through to receipt). 3. Implementation of the redesigned checkout flow in the new storefront app. On 1) and 2) lots of planning and design work has already been completed. The technical design is in place and [documented in Notion](<https://www.notion.so/holdbar/Storefront-web-2-0-architecture-2e9657695d59807fac5cc0cfee627981?source=copy_link>). The first few lines of code have been written. @mgj is doing this work. The design work has also [come a long way already in FIgma](<https://www.figma.com/design/qI4RlYv8t2qLbc0MWHZIBO/Core-Workfile?node-id=18676-96639&p=f&t=8XtbLyZYNJ8GTuqo-11>) by @sari. Mostly for mobile so far. Immediate next steps are to: * Prepare desktop designs (relatively low fidelity) so we roughly know where desktop and mobile differs and how. * Explore more in depth how all the little details should work in practice. This involves looking at existing functionality but also looking over customer insights and opportunities to produce a checkout flow that solves more problems that the existing. * Build and deploy the new storefront in our web infrastructure. We plan on building the terms and conditions pages first as a proof-of-concept and route traffic to them.