Curious why you didn't go native when it's undoubtedly reaper than the stack you chose. The default blank navigation view project would get you 80% of the way with its couple dozen lines of code. And you would get system font, SwiftUI predictable layout, easy database access, and a smaller Binary by a factor of 10x most likely.
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.
Now if someone could find a way to read the scrawled engineer's names etched on the inner part of the vinyl so I could figure out what edition I have in under an hour, I'd be really happy.
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.
12 comments
[ 10.6 ms ] story [ 34.1 ms ] threadAnd it's a RN app:
> It’s a React Native app built with Expo and TypeScript. Data lives in SQLite.
Instead, and I’m not against AI, AI slop that isn’t native, has awful design and awful font decisions.
Someone should take the idea but implement it properly.
And a Cover Flow view is a must.