Tag: iphone

More icons won’t work

Insightful. Screens of icons isn’t scaling, most apps will never make any money, and at this point it’s mostly a sucker’s game.

The idea of having a screen full of icons, representing independent apps, that need to be opened to experience them, is making less and less sense. The idea that these apps sit in the background, pushing content into a central experience, is making more and more sense. That central experience may be something that looks like a notification center today, or something similar to Google Now, or something entirely new.

Iphone self-owns

your jesusphone will naively try to connect to a computer and immediately sync data any time it is plugged into a USB port for charging, which of course can be exploited. the simplest solution is to get a device that doesn’t suck, or you can get some awkward “adapter”.

Cheap smartphones

The high margins that Apple and Samsung get on the smartphones are going to be eaten away by companies like HTC, Huawei, and others to be named. They’re going to introduce smartphones that are almost as good and most people are not going to be able to tell the difference.

it’s getting time to stop being so attached to your jesusphone, because expensive smartphones will disappear in a few years. the Moto G is a harbinger of this trend. it is good enough for most people and < $200.

Peru jesusphones

a woman’s iPhone stolen at a bar in San Francisco turned up a few days later in Lima, Peru. The owner of the biggest phone trafficker is an ordained minister. He aims to open his own church focused on outreach to convicts, alcoholics and the homeless.

the gospel of 2013

Gratuitous API Differences

I think it’s safe to say that MacOS is more source-code-compatible with NextStep than the iPhone is with MacOS. It’s full of all kinds of idiocy like this — Here’s how it goes on the desktop: NSColor fg = [NSColor colorWithCalibratedHue:h saturation:s brightness:v alpha:a]; [fg getRed:&r green:&g blue:&b alpha:&a]; [fg getHue:&h saturation:&s brightness:&v alpha:&a]; But on the phone: UIColor fg = [UIColor colorWithHue:h saturation:s brightness:v alpha:a]; const CGFloat *rgba = CGColorGetComponents ([fg CGColor]); // Oh, you wanted to get HSV? Sorry, write your own. It’s just full of nonsense like that. Do you think someone looked at the old code and said, “You know what, to make this code be efficient enough to run on the iPhone, we’re going to have to rename all the classes, and also make sure that the new classes have an arbitrarily different API and use arbitrarily different arguments in their methods that do exactly the same thing that the old library did! It’s the only way to make this platform succeed.”

jwz on the gratuitous api differences between osx and iphone / ipad