# design consistency Published articles for design consistency. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Facebook's Design Didn't Evolve--It Regressed DevFeed: [Facebook's Design Didn't Evolve--It Regressed]() Original publisher: [Read original article]() Author: Louise North Published: 2026-07-14T12:19:00Z Content type: opinion Language: en Sources: [Web Designer Depot]() Topics: [User experience (UX)](), [Usability](), [Web]() Tags: [algorithmic-feed](), [cognitive-load](), [design](), [design-consistency](), [design-systems](), [digital-products](), [engagement-vs-usability](), [facebook-ux](), [feature](), [feature-bloat](), [interaction-design](), [interface-design](), [mental-models](), [personalization](), [product-design](), [social-media-ux](), [usability](), [user-control](), [user-experience-design](), [ux](), [ux-case-study](), [ux-regression](), [ux-strategy](), [ux-usability](), [ux-ux-usability]() ### AI overview The article argues that Facebook's design regressed as it replaced a predictable chronological feed with opaque algorithmic ranking and accumulated features that fragmented the experience. It presents predictability, transparency, usability, and user control as essential UX principles. ### Source excerpt Facebook didn't get worse overnight--it optimized itself into confusion. What started as the clearest social experience on the web slowly became a noisy, unpredictable system users no longer fully understand. This is what happens when engagement wins over usability--and it's a warning for every designer building products today. ## Figma Make is now available in Figma for Government DevFeed: [Figma Make is now available in Figma for Government]() Original publisher: [Read original article]() Author: Figma Published: 2025-12-11T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Accessibility](), [User interface design](), [Usability](), [Security]() Tags: [accessibility](), [collaboration](), [design](), [design-consistency](), [executive](), [fedramp](), [figma](), [government](), [prototypes](), [prototyping](), [public-sector](), [resources](), [security](), [speed](), [standards](), [tools](), [tools-and-resources]() ### AI overview Figma Make is now available in Figma for Government, enabling government teams to create interactive prototypes, collaborate securely, and test ideas more quickly while modernizing public services. ### Source excerpt With Figma Make now available in Figma for Government, teams can prototype faster, collaborate securely, and accelerate progress on modernizing public services. ## Nick Butcher and Roman Nurik on design consistency DevFeed: [Nick Butcher and Roman Nurik on design consistency]() Original publisher: [Read original article]() Author: Juhani Lehtimäki Published: 2017-09-03T19:03:40Z Content type: opinion Language: en Sources: [Android UI Patterns - Medium]() Topics: [ui](), [Android](), [consistency]() Tags: [android](), [design](), [design-consistency](), [ui]() ### AI overview This article discusses Android design consistency, including how to follow Holo guidelines without making every app look identical. It explains how to preserve brand identity across platform versions while still making an app feel like Android, including the use of custom accent colors with standard Holo widgets. ### Source excerpt In yesterday's Android Design in Action video podcast Nick Butcher and Roman Nurik talked about design consistency on Android. This is a topic that keeps popping up in many design discussions and seems to be often misunderstood. What does it mean to follow the Holo guidelines when building an app? Does it mean that every app must look the same? What if you are publishing your app on multiple platforms? How do you make sure that your brand is consistent throughout the different app versions but still make your app feel like an Android app? Nick and Roman explain how to approach different parts of your app design to achieve all these goals. You can find the video from here (direct link to the design consistency part of the video) and the presentation slides are available here. In a related G+ post Nick gives some tips about choosing colours for your app: "The Holo visual language does not dictate a strict colour palette. While it does provide some base colours as a starting point [0], it is not prescriptive. You should use colour to bring your own brand's personality to your app.One technique that works particularly well is to use a single strong accent colour to marry Holo's visual style with your brand. By default, Holo widgets use a blue accent colour -- but they don't have to! By theming the standard widgets with your own accent colour they will appear both distinctly Android and completely branded." Read the full post here. Originally published at www.androiduipatterns.com on July 17, 2013. Nick Butcher and Roman Nurik on design consistency was originally published in Android UI Patterns on Medium, where people are continuing the conversation by highlighting and responding to this story.