I’m trying to revive Shopster, an app we launched 2013, and I’m writing througout the process. If this is the first post you see, you can start here.
After some time, I finally submitted Shopster 1.2 for App Store review. As I write this, it’s currently “In Review”, and I expect it to be available soon.
I wanted to wrap up this series with a summary of the changes and what I expect to do in the future.
I took some baseline metrics before I started. Here’s the final summary:
- I started using Swift. All new classes were written in Swift, and one small refactor (code I moved out from the AppDelegate) was rewritten in Swift as well.
- There are some shell scripts, JSON files, etc, that were not present before. I integrated fastlane.
In the process, I also removed some third party dependencies we used. The app is now much tighter and less dependent on third party code that I don’t manage.
I solved all the deprecation warnings except one: I’m still using
ABCreateStringWithAddressDictionary. As far as I can tell, the suggested replacement (
CNPostalAddressFormatter) doesn’t quite cover my use case. I’ll review it in the future, and maybe rewrite that method, as it’s not that important for the app.
UI and AutoLayout
All the screens now use Auto Layout. Where there were animations that changed the
frame, I changed to update the constraints and animate that change instead.
Short Term Work
Here’s a short list of things I’d like to tackle in the near future (wihtout counting major architecture changes such as using CloudKit):
- Start using the default system font (San Francisco) instead of the custom font we are using.
- Adopt Dynamic Type across the app.
- Remove some graphics I think make the app look dated, like the logo on the Navigation Bar.
- Localise the app in Spanish1. It’s currently English only.
- Fix the missing deprecation warning.
- Use the new location based notification trigger. Currently, we observe significant location changes, and when they match the areas we want, we trigger a Local Notification immediately. The new
UserNotificationsframework, allows you to set a location as a notification trigger, which would help eliminate part of this code. Since this is core to the app, I didn’t want to take on it now, as it will require more testing.
- Add a new onboarding screen. As soon as you start the app, you need to allow location services and notifications. We simply throw the system dialogs to the user. We can do better.
@3xassets. I didn’t have them, and wanted to ship soon. They’ll come at a later update.
- Make the app free, and show ads only to new users (the ones who got the app for free, basically).
Long Term Work
This list is shorter in items, but way harder, so I don’t know if or when I’ll do it:
- Take on major refactors for the app. Adopt MVVM.
- Start using CloudKit for sync.
- Adopt a freemium model, where a one time payment unlocks some functionality.
- Don’t let your apps rotten! Either pull them from the App Store gracefully, or spend the required time to keep them up to date at the very least through major OS versoins.
- It’s hard giving up on an app you put effort on. I couldn’t, that’s why this version is on review. This is probably not the best example to follow.
My native language! Shameful. ↩