When “Good Enough” - Just Isn’t Good Enough

Eväkallio uses examples from art history to argue that skills transfer between mediums, but mastery takes learning each medium’s conventions. Web interfaces often require inventing patterns, while mobile users expect familiar behaviors shaped by platform guidelines and established apps. Small deviations can feel noticeably wrong.

React Native can reduce development time and cost, including by letting teams reuse expertise and maintain one codebase. But teams drawn mainly to efficiency may underinvest in user experience. Eväkallio argues that React Native has tradeoffs against native tools, yet can still deliver a strong experience when teams put in the work.

Eväkallio describes maturity as the ability to build good products within real constraints. It includes caring about users, studying successful apps and platform guidelines, and testing the experience during reviews. Design, engineering, and management all need shared responsibility, with enough time and budget for the work.

Eväkallio recommends setting realistic expectations, designing collaboratively, validating with users, and building a component library that teams can refine. Shipping an app begins an ongoing process of iteration. He uses Cézanne’s repeated studies of bathers to illustrate how sustained improvement can move a product beyond merely acceptable.