eelco

Check the logs. It is downloading another 3GB of stuff.

Framer is “just” HTML/CSS/JavaScript. This means you can also do things like embed (moving) GIFs, videos and use (almost) all browser APIs in Code Components.

It still works, Beamer uses a different part of the AirPlay protocol ‘suite’. We’ve tested with the betas to ensure it would. (I’m one of the developers.)

So, in the EU and US the average amount spent is above the average amount earned. I'd be more interested in more data on that than what OS was on their phones.

The partially unusable screen acts nicely as an easy to hit back button offering context about where you'll go back to. The spatial organization and animation showing the menu adds even more context, making this way of implementing a 'global' menu a pretty clever design all in all.

My only gripe with it that it might make it too easy to bring the complexity of big menus of the desktop to mobile device. As programmers we're (hopefully) all aware about the power and dangers of using globals.

That's not an option button on iOS. It leads to a menu of 'secondary' menu items, that are hierarchically on the same level as the other tabs.

I completely agree with you, but the user might have been trained by his iPhone to relate the speed of the spinner to the data transfer speed. (The spinner in the status bar of the iPhone indicating network activity has a different speed when you're on EDGE or GPRS versus when you're on 3G).

Utrecht, a whole city to buy your art supplies.

iOS and all the apps are build for a specific _physical_ size. A larger screen would mean apps would need to scale (or run in an awkward smaller size) which would look terrible and be awkward to use (very large buttons). The alternative would be to ask developers to make another, slightly larger version of their apps. Not going to happen ;)

Either that, or you're still in school. (Not kidding, BB is very popular with teens, at least here in the Netherlands.)