Bento
Sara Levin, CEO
air-up.com
David Molinero
2. Air up struggled to increase Conversion Rates with the legacy platform
1. Air up was not able to move fast enough, implement new features at speed and run experiments effectively
3.Changes in the legacy CMS had to be applied manually up to 11 times
4. The legacy CMS allowed to build interfaces using drag and drop which caused UX ownership issues
5. There was a strong coupling to the CMS and other external third parties
Air up & Challenges
6. Lack of automation and suboptimal testing strategy, particularly browser tests
Tech choices
- TypeScript / Kotlin
- Next.js
- App router, server actions
- Rest & GraphQL integrations
- Vitest & PlayWright
- Tailwind CSS
- Shadcn
- ...
Third parties
- Netlify → Vercel & AWS
- Builder.io → Contentful
- Datadog, Sentry, Pagerduty
- GTM & MixPanel
- Unleash
- Figma
- ...
RFC Process to collaborate on building the new platform
RFC Process to collaborate on building the new platform
Engineering 🚀
- Automated release process
- Trunk based development
- Hexagonal architecture
- New testing strategy
- Test Driven Development
- Pair programming
- Functional programming
- Feature flags, etc.
Improved engineering practices
Improved DORA metrics
Architecture (C4 diagrams)
Architecture (C4 diagrams)
Architecture (C4 diagrams)
Architecture (C4 diagrams)
Architecture (C4 diagrams)
Architecture (C4 diagrams)
Architecture (C4 diagrams)
Architecture (C4 diagrams)
Hexagonal architecture & Testing strategy
Overall structure
Integration tests for adapters
Running the app & browser tests without real third parties
Running smoke and synthetic tests in a real environment
Roll out strategy
Roll out strategy
Roll out strategy
Roll out strategy
Roll out strategy
Roll out strategy
NFR
NFR
- Reduced operating costs
- Improved scalability
- Improved performance
- Improved observability
- Improved conversion rates
QA?