PUBLIC MARKS from Spone with tag "design pattern"

In short, passwordless login replaces the username and password combination with a variation on the reset password flow already found on many existing sites. To login, a user enters their email address or phone number. A link is sent to that address that, when clicked, causes the user to be logged in. No password is ever collected or stored.

When AppCache arrived on the scene it gave us a couple of patterns to make content work offline. If those were the patterns you needed, congratulations, you won the AppCache lottery (the jackpot remains unclaimed), but the rest of us were left huddled in a corner rocking back & forth.

I've spent some time thinking about how a web application should be architected. How should it look from a high level? How does the development cycle look? How does the deployment process look? I read a lot about how applications should be modular, and I agree with this, but in practice I've come to realize I don't know how a large application should look.

While Rails may be the perfect tool for building an MVP, it isn’t optimised for medium and large codebases. We’re solving these problems with 3 concepts we believe should be part of any “Advanced” Rails deployment; Interactors, Policies and Presenters.

Your data model has started to stabilize and you're in a position to create a public API for your web app. You realize it's hard to make significant changes to your API once it's released and want to get as much right as possible up front. Now, the internet has no shortage on opinions on API design. But, since there's no one widely adopted standard that works in all cases, you're left with a bunch of choices: What formats should you accept? How should you authenticate? Should your API be versioned?

Carousels, image rotators, sliders, featured content modules, whatever the hell you want to call them — they’re everywhere on the web. There’s a 95% chance you’ve created one. But despite being so omnipresent, little is said about our splashy little auto-rotating frenemies. Let’s fix that.

Patterns, resources and news for creating responsive web experiences.

Here’s some of the more popular techniques for handling navigation in responsive designs

A JavaScript pattern and antipattern code collection that covers function patterns, jQuery patterns, design patterns, general patterns, literals and constructor patterns, object creation patterns, code reuse patterns (upcoming), DOM and browser patterns (upcoming).

In this post, I'll be discussing both intermediate and advanced patterns and approaches for namespacing in JavaScript.

This is androidpatterns.com, a set of interaction patterns that can help you design Android apps. An interaction pattern is a short hand summary of a design solution that has proven to work more than once. Please be inspired: use them as a guide, not as a law.

a collection of design patterns I've found in games.

Standard is a library of pre-built interface controls, layout directives, and human interface guidelines that can be used to build highly standardized and usable interfaces for the web. It is analogous to the generic styles and guidelines made available to developers in the iPhone SDK.

This book is not directly about information architecture—although you will find information architecture principles alluded to throughout. This book is also not directly about visual design—although you will find that the backdrop of good visual design is assumed throughout. This book is about interaction design: specifically, interaction design on the Web. And even more specifically, about rich interaction design on the Web.

The project core consists of a collection of currently 48 design patterns that describe the functional aspects of graphic components for the display, behavior and user interaction of complex infographics.

We're thrilled to be sharing patterns and code with the web design and development community, we hope it's useful, and we look forward to your feedback.