The real pressing identification experience is tilting the record under a lamp at 15 different angles while squinting, then finding out the Discogs entry is wrong anyway. No app can fix that.
Fair question. I know TypeScript, I don’t know Swift. This was my first mobile app and Expo lowered the barrier enough for me to actually ship it. I’m sure native would have been leaner, but I’d probably still be reading SwiftUI docs instead of having an app on the App Store.
The AI wrote the code, but the design decisions are 100% mine, I’m going through a monospaced phase.
Cover Flow would look cool but I’m not sure it solves a real problem for this use case. When you’re digging through crates you want to search and filter fast, not swipe through covers. Appreciate the feedback though!
This was my first mobile app so I can’t really compare, but Expo was a great way to get started with zero mobile experience. That said, I did feel a bit locked into their ecosystem. Everything is designed to push you toward their cloud build service (EAS), and I just wanted to build locally.
Funny enough this was my first mobile app ever, I figured it out doing it. Expo helped a lot. The Apple review process on the other hand… that was a whole learning experience on its own.
Fair enough on the iOS mention. The tech stack (React Native, Expo, TypeScript, SQLite) is detailed in the blog post, I wasn't trying to hide it.
As others pointed out in the thread, RN renders actual native views, not a webview. For this use case: browsing a local SQLite database offline, it works really well.
