A user suggests implementing a voice-based quick add flow to reduce friction when logging subscriptions, making the process feel almost instant.
I’ve been designing my first iOS app recently and it ended up becoming a small case study in simplifying financial information. The app is a subscription manager. The main design challenge wasn’t building the features, but figuring out how to present spending information without overwhelming the user. A few design decisions I experimented with: • Showing yearly spending as the primary metric instead of monthly. I noticed that large numbers tend to create stronger awareness of subscription costs. • Keeping the subscription detail screen minimal. Instead of showing lots of metadata, it only focuses on price, next payment, and small contextual insights. • A voice-based quick add flow to reduce friction when logging subscriptions. The idea was to make adding something feel almost instant. • Using grouped cards instead of complex dashboards so the information hierarchy stays clear. One thing I struggled with was balancing insight vs simplicity. Subscription apps often become mini financial dashboards, which I wanted to avoid. I’m still iterating on the UX and would genuinely love feedback from designers here. Do you think the hierarchy makes sense for this kind of problem, or would you approach the information architecture differently?