pfctdayelise + design   17

The Elements of UI Engineering - Overreacted
Consistency, responsiveness, latency, navigation, staleness, entropy, priority, accessibility, internationalization, delivery, resilience, abstraction
ui  design 
21 days ago by pfctdayelise
Dementia Enabling Environments Project (DEEP) | Alzheimer’s WA
The Dementia Enabling Environment Project (DEEP) Virtual Information Centre provides practical tips, guides and resources to help make the places where we live more dementia enabling. This will encourage a person with dementia to lead as full and independent life as possible. These can be simple modifications that anybody can make to their home, to landscaping or architectural design changes. Use this site to explore different home settings and learn more about key design principles in each area of the house and to download useful information and resources.

The Dementia Enabling Environment Project can help you develop an enabling environment for a person living with dementia. It can make a significant difference to their independence, quality of life and wellbeing.

A well designed environment, planned with cognitive impairment in mind, can help maintain abilities and provide meaningful engagement by providing essential prompts, accessibility and reduce risks to support a person with dementia. A poorly designed environment can be confusing, disorienting and at worst, disabling and even dangerous for those with dementia.
dementia  design 
october 2018 by pfctdayelise
Resource Oriented Design  |  Cloud APIs  |  Google Cloud Platform
The goal for this Design Guide is to help developers design simple, consistent and easy-to-use networked APIs. At the same time, it also helps converging designs of socket-based RPC APIs with HTTP-based REST APIs.

Traditionally, people design RPC APIs in terms of API interfaces and methods, such as CORBA and Windows COM. As time goes by, more and more interfaces and methods are introduced. The end result can be an overwhelming number of interfaces and methods, each of them different from the others. Developers have to learn each one carefully in order to use it correctly, which can be both time consuming and error prone.

The architectural style of REST was first introduced in 2000, primarily designed to work well with HTTP/1.1. Its core principle is to define named resources that can be manipulated using a small number of methods. The resources and methods are known as nouns and verbs of APIs. With the HTTP protocol, the resource names naturally map to URLs, and methods naturally map to HTTP methods POST, GET, PUT, PATCH, and DELETE.

On the Internet, HTTP REST APIs have been recently hugely successful. In 2010, about 74% of public network APIs were HTTP REST APIs.

While HTTP REST APIs are very popular on the Internet, the amount of traffic they carry is smaller than traditional RPC APIs. For example, about half of Internet traffic in America at peak time is video content, and few people would consider using REST APIs to deliver such content for performance reasons. Inside data centers, many companies use socket-based RPC APIs to carry most network traffic, which can be orders of magnitude higher than public REST APIs.

In reality, both RPC APIs and HTTP REST APIs are needed for various reasons. Ideally, an API platform should provide best support for all APIs. This Design Guide helps you design and build APIs that conform to this principle. It does so by applying resource-oriented design principles to general API design, and defines many common design patterns to improve usability and reduce complexity.

NOTE: This Design Guide explains how to apply REST principles to API designs independent of programming language, operating system, or network protocol. It is NOT a guide solely to creating REST APIs.
api  design 
march 2017 by pfctdayelise
John’s Phone – Blog – BERG
It’s a really immediate product: the entire front face is devoted to the keypad and physical interface. The top of the phone has an LCD display, positioned much like an old-fashioned pager; the side of the phone, which you can just see in the pictures above, has a rocker switch for volume, a SIM card slot, a switch for the ringer volume, and a power switch.

The phone makes its intention clear: the immediacy of use and that interface is more important to it than any screen or display-based interaction. It’s all about phone calls and phone numbers.
mobile  design  hardware 
november 2010 by pfctdayelise

Copy this bookmark: