Data is useless without the ability to visualize and act on it. The success of future industries will couple advanced data collection with a better user experience, and the data table comprises much of this user experience.
Many Android and iOS apps have horizontal scrolling lists. Maybe it’s also combined inside a vertical list. But is it necessary? Even assuming it is, are you doing it right? In this article, let’s discuss tips to remember when designing horizontal lists. Later, we’ll look at possible alternatives that can work better.
One night while driving through a dark desert road, I missed a sharp right turn and ran straight into the ditch. The warning sign, placed shortly before the turn, was barely visible under the cover of darkness.
Fractal is a tool to help you build and document web component libraries, and then integrate them into your projects. Component (or pattern) libraries are a way of designing and building websites in a modular fashion, breaking up the UI into small, reusable chunks that can then later be assembled in a variety of ways to build anything from larger components right up to whole pages. Fractal helps you assemble, preview and document website component libraries, and then integrate them into your web sites, apps and build processes to create joined up, ‘living’ projects. Fractal can be run from the command line or integrated into your project via its API.
Dark Patterns are tricks used in websites and apps that make you buy or sign up for things that you didn't mean to. The purpose of this site is to spread awareness and to shame companies that use them.
Inline validation informs users whether what they type is valid as they type. The theory is that it’s easier to fix errors as soon as they occur instead of waiting until submission. The thing is, inline validation causes several problems:
We’ve been running Design Sprints for a long time and value their ability to tackle challenges and fast-track processes. With this in mind, we’ve put together The Design Sprint Canvas - a handy tool that you can download to help guide facilitators and Sprint participants through the process.
Few things in the frontend world are as hot as Design Systems, the idea of building a design spec or library of reusable components that can be shared across a team or company. Design Systems enforce style and branding guidelines, reduce design fatigue for engineers, and consolidate component engineering to one single set of components and a team that builds them. Basically, they help teams manage design at scale.
Reusable Web Components and Design Systems are hardBuilding, Maintaining and Sharing reusable Web Components or Design Systems are expensive tasks. The build setup is a PhD project, the tooling is straigth out of FisherPrice® and packaging everything together requires knowledge that goes way beyond useful front-end development skills.We believe there is a better way...WebComponents Studio is on a mission to streamline and empower the creation of Web Components and Design Systems. Reusable components are about productivity and agility. Let's forget about the unnecessary complexity and slowdown of the underlying plumbing and let's focus on coding beautiful components with built-in quality, accessibility, user-experience and developer-experience.Join the discuss on Slack
Among the many (many, many) points Ursula Franklin makes in The Real World of Technology, she suggests that technology is best understood not as software or gadgets, but as a practice: as a way of doing something.
It’s fairly possible to judge a component and say that it’s easy to implement it in HTML&CSS. I agree, it’s easy when you are working for practice purposes only, but for a real-life project, it’s completely different. The perfect responsive component that you just built will fail quickly in case it was used for a real-life project with real content. Why? It’s because judging on how a component can be built without considering the edge cases.
Anyone who's worked in game development for a while knows that launching games is challenging. Creating online games is even more difficult, as it requires building Internet services like matchmaking, account systems, chat services and many more. Guild Wars, an online Role-Playing Game I helped develop at ArenaNet, requires ~30 backend services, and its sequel, Guild Wars 2, has ~80! By the time I left ArenaNet Guild Wars 1 included 6.5 million lines of code, which is about one-fourth of the number of lines in the Linux operating system kernel!