In my opinion Curve has a bit of a problem with the way it delivers messages to its users via the app. A lot of important information, such as maintenance breaks or details on declined transactions are usually delivered as notifications, which are ephemeral by their nature, while they should be easily accessible every time user needs them. What I suggest is creating some sort of an inbox for these messages directly in the app. It could be accessible as a small icon in the corner, which clicked on, would open a simple list of messages.
The messages in the app could include for instance:
- information on maintenance breaks,
- details on declined transactions (why was it declined?),
- requests from the Curve team and replies to support tickets,
- updates in the service itself and its T&C.
Currently, the way Curve team communicates with users is really unclear. A lot of news are only sent by e-mail, other times it’s only an in-app notification. Support is offered by e-mail too, except there’s also a live chat now (I haven’t used it yet though). On the top of that, there’s this forum most Curve cardholders probably don’t even know about. One simple place to send and receive information from the team (and some more advanced app-generated info as well) would absolutely change this perspective and make Curve a more trustworthy product. I know that by describing what I mean some parts of it might have been omitted, so I’ve drawn the way it could look.
Ad. 1: a simple icon would make the feature easily found. If there are any unread messages, it could be indicated by a number on the envelope icon.
Ad. 2: inbox consists of the list of messages received from Curve. The icons could indicate the type of message; if it’s app-generated or written by a human, what type of information it contains. User wouldn’t be deleting any messages, they would disappear when they are no longer needed (there would be a pre-set expiry date, 30 days after delivery or in some cases more).
Ad. 3: the message view could be made with a simple WebView. That provides flexibility to send new types of content without changing the source code of the app itself.