logoalt Hacker News

jimbo_joe • today at 11:29 AM • 0 replies • view on HN

The sentiment is somewhat understandable, especially in the world of fast-moving AI-enabled companies all around us. The example doesn't really sound motivating out of the gate.

> All three teams adhered to the corporate branding guidelines, so their products look and feel reasonably similar. They also work fairly well and were shipped on time. This is the opposite of how things play out in most of the world's large companies, from any major bank to supposedly tech-savvy giants like Google. Every time you cross an app boundary or even a team boundary within a single product, all bets are off. At best, the UI differs in small, annoying ways (button styling, UI element rounding radii), or at worst, you need to go through separate login and payment flows.

> whenever the user switches from the account view to the investing tab, a whole new JS framework is loaded. But, given all other factors, this is an acceptable trade-off. I guess it's acceptable if you are going from one major product to another, but accepting this when switching between parts of an application that are supposed to be coherent (same banking app, same money involved) tells the customer that you don't care about their experience that much. Accepting this also massively increases the chances that the UX will be different, since frameworks tend to come with their own patterns that shape developer thinking.

Of course, it's OK to repeat yourself as many times as needed to keep shipping products that affect the bottom line of the business and help customers achieve more. At the same time, as a company transitions to multiple products or breaks up the monolith of its main product, it should also start building the DNA for maintaining a coherent UX. This is less about using the same technologies under the hood and more about crystallizing the foundational API shapes and packaging them in a way that allows teams to offer customers a consistent set of UX expectations across internal company boundaries.

In practice, this means that some choices have to be made in a BDFL-style fashion: one general-purpose OLTP database with a preferred way of interacting with it (ORM or not), one JS framework with components supporting shared data structures (with escape hatches for specialized use cases), and one opinionated design system covering the vast majority of use cases across the company's major products.