Product Decisions: Avoiding Document Hubs and Notification Centers in Financial Apps

The Problem with Common App Features

The author identifies 'document hubs' and 'notification centers' as two features to avoid in consumer-facing financial services applications. These features, while seemingly straightforward, often become complex and difficult to maintain, ultimately providing a poor user experience.

Document Hubs: Rebuilding Google Drive

Document hubs typically arise from the need to store legacy PDFs and comply with 'persistent communications channels' requirements. What starts as a simple list of files often escalates into a complex system with tagging, archiving, printing, and sharing functionalities, akin to rebuilding a full document management system like Google Drive. This complexity introduces significant security, authentication, and maintenance challenges.

Notification Centers: A Bad Gmail Clone

Similarly, a simple request for a 'bell icon with a red dot' for notifications can quickly evolve into a poorly implemented messaging system. Both document hubs and notification centers create substantial ongoing maintenance overhead, especially with continuous updates from operating system providers like Apple, Google, Microsoft, or Amazon.

Overcoming Stakeholder Expectations

Convincing stakeholders to abandon these common mental models, even when customer focus groups might validate them, is challenging. The author suggests that illustrating the long-term running costs, rather than just the initial build costs, is an effective strategy to demonstrate the financial burden and complexity these features introduce.