pngat2x

"Comp" or "layout" would be the more technical terms for that, though I've found they're generally less understood.

https://en.wikipedia.org/wiki/Comprehensive_layout

http://www.apple.com/business/docs/iOS_Security_Guide.pdf

Page 41, Second paragraph: "The keys, and the file’s metadata, are stored by Apple in the user’s iCloud account. The encrypted chunks of the file are stored, without any user-identifying information, using third-party storage services, such as Amazon S3 and Windows Azure."

You could just author a DVD.

http://www.hometheaterforum.com/topic/216350-what-dvds-actua...

Edit: Here's a bit more detail on the capabilities: https://documentation.apple.com/en/dvdstudiopro/usermanual/i...

OSHA probably wouldn't have much to say… The peak he measured would only be outside of their guidelines if the attendants screamed for the entire LAS-SFO flight and then he hopped on a plane and immediately flew back with the same treatment.

Table G-16 - Permissible Noise Exposures

https://www.osha.gov/pls/oshaweb/owadisp.show_document?p_tab...

DOS is the primary interface on some of the instant-replay servers used for broadcast video. People know how to use it, after a decade or two in production. There are some more current web interfaces and client tools, as well.

Here's a manual with some fun screenshots from the EVS XT3 [1]. Apparently 196 of them were used together at the World Cup last year [2].

[1] http://www.evs.com/sites/default/files/download_area/package...

[2] http://sportsvideo.org/main/blog/2014/06/broadcast-asia-2014...

I've built my experience mainly through exposure to native mobile. I find that the walled gardens and constraints you work within tend to help focus what you're creating. It's easier to tell when something looks or feels "wrong" when you're looking at apps that are built to match the OS's ecosystem, instead of the latest web trends.

When you work with a standardized set of UI elements on a canvas of limited size, you tend to start thinking about the interface in terms of modular actions and tasks, which you can repurpose later when scaling up to tablet or desktop web. You also have a good basis to simplify these tasks further when branching out to wearables and in-car devices.

----

At this point, Google, Apple, and Microsoft each have pretty defined ideologies and UI — check out their guidelines:

https://developer.android.com/design/material/index.html

https://developer.apple.com/library/ios/documentation/UserEx...

http://dev.windows.com/en-us/design

----

Check out some of the sessions from WWDC and Google I/O too:

https://developer.apple.com/videos/wwdc/2014/

https://www.google.com/events/io/io14videos

----

There are also a lot of great blogs out there that have pinpointed info on different parts of interface design. Sometimes these info-morsels can be easier to digest than starting a full course in UX. This is definitely not a comprehensive list, so look around, and get your RSS client fired up.

http://www.uxbooth.com

http://alistapart.com

http://usabilitypost.com

http://52weeksofux.com

http://www.smashingmagazine.com

http://viget.com/inspire

http://www.adaptivepath.com/ideas/

http://karenmcgrane.com

http://ustwo.com/blog/

----

Luke W's notes from conferences are usually pretty informative, and he has articles going back to the early 2000's, for extra perspective.

http://www.lukew.com/ff/

----

If you want info on actual implementation, at least in Photoshop, you can't do better than usTwo's Pixel Perfect Precision handbook and Marc Edwards' articles:

http://ustwo.com/ppp/

http://bjango.com/articles/

Using Google Voice as an inbound SMS-to-email bridge for running contests, etc.

I've seen 2k+ inbound messages/day put through a service that does this, versus the business paying ~$20-50/month for Twilio.