Goodbye, Metro
Last year, I built an app for the Dubai metro, tram, and monorail. It had all stations on a map, fare information, and news, which I never updated since the first release.
Over time, I forgot about the app. The fares changed, stations got renamed, new things happened. But I never got a chance to update. It wasn't a very well-built situation. The app pulled JSON from a server, cached it on the device, checked for updates on start, but could fall back to cached data if no internet.
Last week, as part of my effort to update older apps, I started updating Metro. Better UX, newer maps, updated data using Firestore; the works. But then I came across this app: Dubai Metro Interactive Map.
I wasn't a huge fan of the UX, but it has a custom map I loved. I used real location coordinates to map the stations and lines, etc., but they followed the Dubai metro's printed maps for their layout. It was pretty cool.
When I built Metro, there were no apps that offered offline support, and most of them looked terrible. That wasn't the case anymore. So I added shutting down useless apps to my list of cleanup activities this year and removed it from App Store and Google Play. It sucked, but it just made sense.
Learnings
- Apps are easy to build but hard to maintain! Especially those that require paying attention to the news for updates. You can't have outdated information there.
- Maps UX is difficult to achieve. Look at the terrible icons I used on my map. I hated them, but it was the best I could do then. There were also many markers flickering around the map whenever it resized (thanks, Apple Maps!) when showing details about a station.
- Sometimes, it's easier to get rid of something than to waste more time on it. Now I can focus more on other apps, loads of which I have planned for this year.
- I need to improve my release process to do releases more often than once a year. And maybe only build apps that I really care about so I can update them regularly. Here's to building more useful and fun stuff in 2019.