Eavesdropping on @Netlify's Headless Commerce Summit, and there's a lot of interesting stuff happening — but it's also telling how much of the headless excitement and messaging centers on "you only have to focus on delivering the best front end experience for your end users".
SUPER COMPELLING for a FED team frustrated by tight coupling with legacy systems or services, but… for people in charge of the whole product (or teams handling that backend stuff) the challenges still gotta be solved, with the added lift of keeping the complexities hidden.
Decoupling and headless approaches can definitely deliver significant advantages — esp. for orgs that really need to use the same pipeline for many different content/interaction endpoints — but the complexity doesn't go away, only shifts around.
Successful decoupled and headless systems I've designed, examined, and swooned over from afar weren't *created* by discipline-silo'd teams; it took a LOT of careful collaboration and planning to make the eventual silo'd work possible.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
