Reminder+ 2.0 Released

Nudg’em v1.2.2 has been updated to 2.0, with the new version renamed as Reminder+ 1. It’s available in the App Store.


What’s new?

The name. The app was originally called Nudg’em, as in, “Nudge Them”. Later, I updated the name in the App Store to be “Send Reminders to Your Friends – with Nudg’em”, to make the sending part explicit.

The app is about reminders, and sending reminders. I wanted the name to be obvious, so opted for “Reminder+” (I kinda like the “+” when used in this way for app names).

Aesthetics. The previous version dates back to iOS 6; v1.2.2 was released on May 2013! v2.0 adds a fresh, iOS 7/8 look, which was obviously required. I also want to re-write the user interface using Auto Layout.

New workflow: compose and send. In previous versions of the app the user could only send an existing reminder. They could create the reminder within the app itself and then send it, or browse those already created, perhaps within the iOS Reminders app or perhaps using Siri.

Whichever way, the reminder being sent had to first exist in their own iOS reminder calendar; that often meant deleting said reminder immediately after sending it. In my view, this was an obvious shortcoming of the app.

In v2.0 the user can simply compose and send, without ever touching their own reminder calendar. I’ve communicated this as choosing to either Compose or Select the reminder to send:

Compose or Select the reminder to send

Improved V.I.P list. In the previous version the user could set a single V.I.P – which resulted in either the email or the message recipient field being pre-populated. v2.0 allows a list of V.I.Ps to be created and the user can select/deselect as desired; it’s also possible to select multiple V.I.Ps.

It’s a small step in the workflow, but when you want to quickly send a reminder, the little things add up.

New In-App Purchase: Send via AirDrop. Reminder+ is freemium, primarily because the recipient of a sent-reminder needs the app to accept it; paid upfront presents a significant barrier to use of the app spreading and continuing.

Pre 2.0 there was a single IAP, “Send via Messages”. It works well as a paywall as the only change is the delivery mechanism. Reminders sent via email work just the same but they’re not as direct.

v2.0 adds a new IAP for sending via AirDrop. It’s a good feature for a number of reasons:

  • If the recipient is in range it really is a fast way to send a reminder.
  • It’s feels good/fun sending stuff using AirDrop (the original reason I wanted to add AirDrop support).
  • Following the same model as Send via Messages, which seems to work, it gives the user something else to buy.
  • Unlike Send via Messages there’s no server component2.

In-App Purchases

I want to develop Reminder+ further and I want that to include additional In-App Purchases – as I’m convinced the app needs to remain free. Within the scope of this project adding Send via AirDrop didn’t require too much additional work, as compared to other ideas in the backlog, making it a good place to start.

Other stuff. As it’s listed in the App Store’s What’s New:

  • List selection for browsing/sending one of your own iOS Reminders.
  • Improved tailoring of iMessage content; if preferred iMessage can be more concise (Send via Messages is an In-App Purchase)
  • Reminder creation inside Reminder+ supports ‘weekday’ recurrence
  • Added support for custom recurrence rules
  • Quick email link for sending feedback (in Settings screen)
  • Bug fixes

What’s next?

The backlog is split into three, general buckets:

  1. Improvements to the base/free part of the app. I want to add both optimisations to the current workflow and new workflows, e.g. list creation.
  2. New In-App Purchases. Beyond the delivery mechanism, I want to add meaningful enhancements to the app, that users can pay for.
  3. Platform expansion. Top of the list would be universal app or functionality for the watch, but this could include translations, for example.

As I wrote in the last post, for now, this is the only app I’m going to be working on. I’m not exactly sure what the next release will look like, especially as I’ve deferred checking out iOS 9 until now, but it will be something from one or more of those buckets above 😉

  1. I wasn’t 100% sure that name would be accepted, but it was, happy days.
  2. I use an Amazon S3 bucket to temporarily store reminders sent via Messages. The message contains a link to the reminder for the recipient to download. Relatively speaking the user base for Reminder+ is tiny – as is the server cost. But it’s there, nonetheless.