"Images used for text" - Ok, what am I missing here? I see fewer and fewer sites using image text every day. And the linked example (weesociety.com) appears to use images only for photos. SVG logo? Is that a problem? Even SVG for the SM icons.
"...but most people do not use iPads to visit websites"
Hmmm.
I love tabasco on the right dish - eggs, gumbo, jambalaya, etc. The oaky taste can get old though. Sriracha has too much garlic and sugar for my tastes.
I think habanero peppers have a great flavor, but the heat usually overpowers them. Removing the seeds and gills, and adding vinegar and/or carrots can tame the heat.
Sorry, but the huge, pixelated N1, along with "We do not have a review yet. Send us your review and if we publish it we will give the app to you for free!" kinda put me off.
I got my daughter an iPhone 5, and although I prefer Android (ICS/JB, anyway; think I'd go with iOS over GB though), I do love the form factor. I've had more than a few near drops with the N4 while shifting position one-handed!
Neat experiment, but I just couldn't deal with the size. I've put my N7 in my pocket, because it does fit, but it's usually part of a joke about the increasing size of phones. Other than the size, the N7 feels quite a bit less responsive than my Nexus 4. I do prefer the N7 for two-handed reading, typing and browsing (and to save battery on the N4).
As somewhat of an aside, I love viewing the large screen on the Nexus 4, but ergonomically, it's just too much. If I can't hit all four corners with my thumb without changing my grip, it's not optimal. I have large-ish hands, but my Nexus One is the perfect size for one-handed use.
I'd love to have a modern, vanilla Android phone with a 4" screen. And without a glass back.
Don't feel bad, on my Nexus 4 I'm redirected to a mobile subdomain and 404'd.
But you probably mean something along the lines of:
"Increasingly, users are accessing the web from a mobile, therefore it's critical that your presence on the web is optimized for mobile devices. Studies have shown that 2/3rds of users will not return to a site that is not optimized for mobile."
That was floated next to a Flash video embed with no fallback. But here's the fallback on YouTube: http://www.youtube.com/watch?v=Ja7abx3OPOQ It was easy to find once I opened the whole presentation in a desktop browser with Flash support, click-dragged back to the page, clicked the magnifying glass icon to spawn the popup, then the More Info tab, then the YouTube icon in the lower-left corner of the video to 'view on YouTube'.
I'd send you a link, but there isn't one. It's all one URL. And you're probably not part of the 1/3 that will return to a site that isn't optimized for mobile anyway.
Yes, especially considering that this particular piece isn't available on touchscreens. The click-and-drag experience is even worse with a laptop trackpad.
They're great if you're using desktop or iOS, but fall short if you use Google's own devices. The mobile playbook serves a phone view to the Nexus 7 tablet, and a broken desktop view to the Nexus 4.
The lag can be unbearable at times. Makes my HP touchpad running CM feel fast. I've had some luck shutting down processes in Settings->Apps. An XDA member reported that his performance and battery life improved after cycling the battery a couple of times.
There are certainly tons of free resources out there, but I'm busy enough that $1/day for 20 days of emails with directed tutorials is more than worth it. Those howto's look like a great resource for more detailed (and varied) info, but I just need someone to guide me (and gently prod me) through the basics.
I signed up to 'keep myself honest' on my commitment to migrate my websites from my Bluehost account to my 3 month old Linode. I'm somewhat comfortable with CLI, but need to fill in some holes and get the practice.
I love my nexus 7, But you're right, most websites assume anything less than <768 is a phone and deliver a single column layout. Even though the n7 is 800px wide (portrait), it reports a device-width of 600px. And of course plenty of websites sniff UA and deliver mobile if they even see Android.
I find off-white a little easier to read, but the sheer amount of light emanating from a large screen anywhere near white irritates my eyes more so than the strain of reading slightly fuzzy fonts.
While I can appreciate the technique, I haven't adopted the use of @2x images for photos. Most photos tend to hold up pretty well when scaled (soft edges and relatively low contrast). If you're serving up a portfolio, sure, but I find more value in maintaining and serving @2x (based on media queries for MDPR > 1.3) for UI elements or logos not easily reproduced in CSS/SVG.
Not a fan of progressive myself, but it should be noted that iOS (at least iOS5), will downsample jpgs larger than 2MP; saving as progressive apparently circumvents this 'feature.'
Foundation's mobile grid utility classes (class="nine mobile-three columns") and source ordering are really nice. And even though BS buttons are prettier, the gradients make a quick color change very challenging!
Wow, I had no clue, but assumed Foundation sprung from BS. I like that Foundation is lighter and easier to override than BS, and even though it has a similar look, it's decidedly different than the stock, ubiquitous bootstrap design. But lack of IE8 support makes it a bit of a hard sell. I'm excited to see what's in store for both frameworks, but hope to see Foundation continue as a leaner, less opinionated alternative.
Not off the top of my head, but give me time - I have only recently started working under a non-technical PM! The synopsis ('code monkeys') nails it from my experience (ad agency).
Nice, I love that they created a large and small version so that the details weren't interpolated away when down sampled. The 'making of' is great, I'm going to forward this to our designers.
I would love to use SVG, but support just isn't robust enough. Hard to deal with hover/active states too. Icon fonts are one request and easy to style with CSS color and text-shadow (even simulating glows). I just wish there was an easy way to generate a small font set from a the handful of vector elements I need for a given website (custom elements, that is, not using a service like Pictos).
I've only been using 2x images for UI elements and logos. Photos still look fine at standard res (especially if 'Saved for Web' with a .25 blur). A recent project included a 25K 8-bit 2x sprite sheet, and a 13K 1x sprite sheet for LTE IE8. So not much of a difference if limited to elements that really need to be crisp.