Pains

Ineffective or cluttered visual hierarchy where every element competes for attention forces users to work harder to identify what matters most, leading to confusion and abandonment before conversion.

Apps fail to provide meaningful error messages or user guidance when operations fail (e.g., payment timeouts, network errors). This confusion causes users to abandon the app without retrying, resulting in lost engagement and poor UX.

Unlike Web2, Web3 has no universal interaction patterns. Every application handles wallet connections, transaction confirmations, and network switching differently, forcing users to relearn basic interactions repeatedly. Inconsistent design makes differentiation difficult.

Developers fail to implement accessibility features like screen readers, voice commands, and high-contrast text, excluding people with disabilities from using the app. This is not just a nice-to-have but a critical requirement for inclusive design.

Designing in isolation without real user input leads to misaligned features and frustration. Assuming what users want without validation is a fast track to failure.

Missing or inadequate FAQs, poor documentation, unclear contact information, and lack of live support leave users without recourse. Long wait times and unhelpful automated responses worsen support pain points.

Users managing assets across multiple blockchains (Ethereum, Polygon, Solana, Layer 2 solutions) must manually switch networks, add new networks, or use bridges. This creates fragmented experiences requiring users to understand network mapping.

JavaScript applications become sluggish due to heavy DOM manipulation, large data processing, or unoptimized rendering in frameworks like React. Developers struggle to identify performance bottlenecks and lack clear optimization strategies.

As multiple teams contribute to large applications over time, components drift in behavior. Buttons, forms, modals, and tables become inconsistent across modules, causing interaction patterns to become unpredictable and maintenance costs to rise.

As JavaScript applications grow in complexity and scale, maintaining modularity and performance becomes increasingly difficult, with no clear architectural patterns or tools to guide developers in managing large systems.

Products fail to customize experiences for individual users and poor recommendation algorithms make content discovery difficult, reducing engagement and causing users to switch to competitors.

Growing applications often have broken layouts, horizontal scrolling, unreadable tables, and inaccessible forms across mobile and tablet platforms. Poor responsiveness directly affects usability and user adoption.

Too many authentication steps in banking and finance apps cause user frustration and drive users to switch platforms. Simplified or biometric alternatives are needed.

Features that don't work as intended, missing critical functionality like appointment reminders, or poorly implemented new technologies (e.g., early AR integration) create frustration and reduce product value.

Figma's March 2025 pricing changes included 20-29% increases for Organization plans, with forced bundling of FigJam and Figma Slides. Teams that don't use these products are now required to pay for them, feeling like they're subsidizing unwanted features—likened to cable TV bundling.

Figma lacks native z-axis and 3D transforms that CSS has supported for years. Designers need paid plugins or third-party workarounds just to visualize basic 3D rotations that developers can implement with a single CSS line.

Figma locks the order of variable collection modes at creation time. Adding a new breakpoint mode after initial creation places it at the end permanently. Reordering requires rebuilding the entire set from scratch, with no drag-and-drop interface.

Figma is adding dev-oriented features like code blocks to Slides while neglecting core design functionality. Long-time users perceive a strategic shift toward developers and coding rather than design, causing concern about Figma's identity and priorities.

Designers work with pixels and layers while developers think in components and logic. This fundamental disconnect causes challenges when translating intricate layouts into maintainable code, compounded by lack of standardized design systems.

Figma's chaotic and non-intuitive interface can feel actively exclusionary rather than empowering, particularly for neurodivergent users. The complex navigation and buried controls create barriers rather than facilitating design work.

Figma's file management remains a significant challenge, with designers spending excessive time organizing files rather than focusing on actual design work. Navigating through projects feels cumbersome, especially when working on multiple simultaneous projects, due to lack of robust folder structures and intuitive grouping options.

Developers struggle to utilize DevOps tools due to inconvenient interfaces, incorrect access controls, or missing documentation. These barriers obstruct routine tasks like gathering infrastructure logs, provisioning environments, and reviewing CI/CD test results, limiting iteration speed.

TLS protocol design is inherently obscure and complicated, making it difficult to audit and easy to introduce bugs. Issues include missing perfect forward secrecy in many TLS 1.2 ciphersuites, client-only authentication by default, and data leakage about session status and party identity.

SNI is only supported in TLS 1.x, not SSL 3.0. Additionally, older clients (MSIE on XP, Java 6, Android versions, and some programming languages) lack SNI support, causing certificate errors when multiple certificates are hosted on the same IP address.