Four Weeks of Building Buildhorn for Shipaton 2026
Buildhorn’s fourth Shipaton update covers RevenueCat subscription testing, Firebase Crashlytics, and Koin cleanup before App Store submission.
It has been four weeks since the work on the Shipaton app began, and the reporter shares an update on the progress. The app, called Buildhorn, aims to deliver CI build failures directly to users' phones. The reporter works with Kotlin Multiplatform (KMP), iOS App (SwiftUI), and Firebase Backend technologies.
During the past week, the reporter focused on testing the RevenueCat paywall and integrating Firebase Crashlytics for crash reporting. These tasks require careful attention to detail and are crucial for ensuring the app's production-readiness.
The reporter made minimal code changes, mostly focusing on refactoring to minimize the chance of bugs slipping through or requiring last-minute tweaks. The reporter recommends this approach for any app's initial release to ensure the best possible outcome.
In this update, the reporter details the following changes:
1. Configured Subscriptions in App Store Connect and imported them into RevenueCat.
2. Updated TestFlight builds to use the RevenueCat Apple API key for end-to-end sandbox testing for subscriptions.
3. Set up Firebase Crashlytics for crash reporting, including tracking when exceptions occur in the KMP layer.
4. Cleaned up Koin DI modules for better logical grouping.
The reporter then delves deeper into each part of the application and how these changes contribute to the overall development of Buildhorn.
Written by urgent.news from HackerNoon's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
