"This isn’t the first time Windows Phone users have been shafted by the Mountain View company not willing to develop for the platform."
Bullshit - this isn't Google screwing over Microsoft, it's Microsoft being idiots. If MSFT built a YouTube app that didn't blatantly violate Google's policies, I don't think it'd be a problem.
YouTube wants viewers, regardless of which platform they're coming from.
Mossberg's got an interesting observation here, but he's missing a really important point: Apple's core profit engine is selling hardware. Amazon and Google make money by selling services and non-hardware goods.
Since Amazon/Google make money regardless of platform, they have an incentive to produce content for Apple's platform. Since Apple only makes a real profit if/when you buy their hardware, they have no incentive to do the same.
"There was once a boy named Milo who didn't know what to do with himself - not just sometimes, but always.
"When he was in school he longed to be out, and when he was out he longed to be in. On the way he thought about coming home, and coming home he thought about going. Wherever he was he wished he were somewhere else, and when he got there he wondered why he'd bothered. Nothing really interested him - least of all the things that really should have."
Except for one issue: it actually slows down the efficiency of the bathroom.
See, by splitting up washing and drying into two steps, you allow two people to be in the process of cleaning their hands at a time.
By bundling the two steps together, you reduce the amount of stuff in the bathroom, but you also reduce the efficiency of the bathroom.
This AirBlade Faucet is a great idea for low-usage bathrooms: less paper towels, less equipment to maintain, etc. For high-volume bathrooms, (airports, etc) this would actually be a step backwards to put these faucets in, if a goal of the bathroom is to be able to quickly serve a large group of people.
Gross headline. I'd hope, at the very least, that a designer would spend more than 10 minutes designing the thing.
That said: I've dropped AFIncrementalStore into a Core Data project, and it was wonderfully easy to add to the project. I'm still getting started with it, but it's proven to be far easier than working with RestKit's setup.
When this was announced a few weeks ago, the University of California added this comment to their Vimeo account:
"Thank you again for all your thoughtful comments and feedback.
To clarify: this new visual approach DOES NOT replace the historic UC systemwide seal. We love the seal. The seal will still be used in all formal systemwide communications, on diplomas, official regental and presidential communications, and other formal applications.
"The two symbols serve very distinct roles. To preserve their gravitas, many of our campuses, and other universities across the country have limited use of their official seals in similar ways. It also does not replace the individual identities of each of our UC campuses. It gives our campuses and others a simple, distinct way to reference the system as a whole.
"We looked at many different solutions, but felt that building off the seal was a great way to honor our history, while also pointing to our strong tradition of pioneering innovation. We’ve done considerable testing on the overall approach, and have generally heard very positive feedback."
---
To me, the new logo looks cheap and flashy, instead of timeless. Universities are some of the only long-lasting institutions that we have, and this new visual style has zero life in it.
Someday, we'll look back at this logo like we look back at bellbottom jeans and denim jackets.
This tutorial is really great. It not only covers UICollectionView, but also walks you through some wonderful design and interface polish. Definitely worth the time.
I also found the double-tap-to-delete counterintuitive. If a single tap expands a node, then a double-tap should open the article. Tap-and-hold to delete is a bit more intuitive, too -- it's the same gesture you'd use on your iOS home screen to delete an app.
Don't play games with this one. If I were in your shoes, I'd pull my binary, too.
You do not want to be waiting on the App Store Review team to fix this. I'm one of the developers in Marco's post; it's been 24 hours and all I've gotten is a boilerplate response from the App Review team.