Archive for the 'Apple' Category

Apple – Making a difference. One app at a time.

Each iOS app offers remarkable — and often delightful — possibilities. But the most powerful iOS apps ever are ones that change people’s lives in ways they never imagined. 

This is pure Apple promo, but we really enjoyed the video – the iPad is a versatile, rugged tool for deploying innovations to places and people who need help: from rural Kenya healthcare to controlling prosthetic legs. Check it out…

Android Fragmentation

John Gruber:

Jonny Evans, reporting for Computerworld:

The BBC Trust today responded to a complaint the broadcaster favored iOS devices when it comes to adding features to its catch-up on demand iPlayer service for Android phones. This complaint was rejected because the Trust found “no evidence” to suggest iOS had been “unfairly favored.”

Instead of pro-Apple favouritism, the Trust found a series of quite logical reasons why Android lagged iOS when new features were added to iPlayer, mostly surrounding the “complexity and expense” of developing for Android.

The company also noted a couple of other logical reasons why developers dealing with limited time and budget would opt for Apple’s mobile OS:

Engagement is higher on Apple devices

Android is fragmented

Android development is complex and expensive

OK, but other than that, how did you enjoy developing for Android, Mrs. Lincoln?

 

Fraser Speirs: iPads and PCs, Beyond Consumption vs Creation

This is a seriously useful analysis by Fraser Beyond Consumption vs Creation – what do you think?

When the iPad first launched, many people reached for a quick analysis that it was a device “only for content consumption”. Despite time and experience having proven those people quite obviously wrong, the debate seems to persist as to what the iPad is, precisely, for.

My own opinion is that the iPad is for about 80% of all tasks you can conceivably do on a computer. I have never thought of the iPad as a distinct entity requiring a total first-principles relearning of what it means to use a computation device.

As I've written before, the question what you want to do with your computer has never had more impact on exactly the device you should buy. Therefore, it's still relevant and worthwhile to ask the question of the iPad: what are you capable of, and what are you best at? Further, as the iOS ecosystem has developed, another question: if I add these accessories to you, what can you do now?

Still, I feel that the consumption/creation split is far too simplistic a curve to grade these devices on. It recognises almost nothing about the user's task beyond whether it's an input task or an output task. There's far more subtlety that we can reach for.

I'd like to propose a more useful pair of axes on which we can place these devices – smartphones, tablets and traditional PCs – than simply consumption/creation. I've been thinking about this for some time and I think it has some usefulness.

Task Complexity vs Task Duration

I'd like to propose that we can look at the 'sweet spot' for each type of device along two axes: task complexity and task duration. Task duration is the more obvious of the two: how long of a continuous period will you be using your device for the task.

Task complexity requires a little more unpacking. When I talk of “complexity”, I'm looking at a combination of factors that make a task complex:

  • The number of steps to completion
  • The extent to which you're combining data from multiple sources
  • The amount of data that is being manipulated
  • The linearity or otherwise of those steps – the less linear, the more complex the task

There may be other types of complex task that I haven't thought about. The exact specifics don't matter too much but these give you the general idea.

Given that, here's a chart of how I think about the 'sweet spot' for each type of device.

So what does this chart really say?

I place smartphones near the origin. They're good for simple tasks done for a middling duration or tasks of moderate complexity for a short period. For example gaming, which is a fairly non-complex task, can be quite acceptable on a smartphone for a reasonable amount of time. On the other hand, editing a spreadsheet on an iPhone can be done but it's not something you'd want to do for a whole day of working. Many of the most effective phone apps that take you through a series of steps do so in a very linear and directed fashion.

The iPad section of the chart has a couple of notable features: the dog-leg area at the top-left and the area at the bottom-right of the chart. Let's dig into those.

Firstly, consider tasks of maximum complexity done over any duration: the iPad doesn't reach into that area of the graph at all. That's simply because there are some tasks of sufficient complexity that the iPad cannot currently be applied to them. The reasons are varied but fall into one of three areas:

  • The hardware is not powerful enough yet. Examples here would include managing an entire high-resolution photographic library in a hypothetical “Aperture for iOS”. The iPad simply doesn't have enough storage to make this possible, although the new 128GB iPad may well take a bite into some of these data-intensive tasks.
  • The software has not been written yet. An example might be doing some CAD/CAM design. Perhaps iOS doesn't offer all the APIs required for some apps yet. We can hope that iOS 7 will start to eat into some of these tasks.
  • App Store policy doesn't allow it. The classic example here is all the programming tools that we might wish to have on iOS which can't be brought wholly to iOS until policy changes.

Similarly, there are tasks of low-to-medium complexity that can be adequately performed on an iPad for long periods of time. Examples might include annotating PDF documents with some of the excellent PDF apps on iOS, or managing photos in iPhoto, composing music in GarageBand, reading iBooks and so on.

In the middle of the chart lies a broad area of tasks which are moderately complex, done for moderate amounts of time. This is where iPad excels and why it is such an excellent computer for schools. I've never argued that any current or past iOS device can “do everything” – patently, it cannot – but I do argue that it can handle 95-100% of everything a computer is typically called on to do in a school setting. The majority of our classes now use iOS exclusively, despite easy access to Mac laptops being available.

Finally, there remain several tasks for which computers are used which tablets remain unsuitable for the reasons listed above. Simply think of the apps that are missing from iPads: Final Cut Pro X, Aperture, Logic Pro, iBooks Author, Adobe Photoshop. These tasks – for now – remain the preserve of the traditional “desktop-class” PC (in which category I include laptops).

For the whole story, please read the Source:
http://speirs.org/blog/2013/3/4/beyond-consumption-vs-creation.

Horace Dediu: Apple is approaching Samsung capital expenditures

Horace Dediu has been writing an important series on Apple and Samsung capital structure. In his 12 Dec 2012 post Horace compares 2006 – 2012 capital expenditures

In the post reviewing Samsung’s Capital Structure I noted that its component divisions have historically taken 90% of capital investments and that the overall capital intensity for Samsung Electronics has increased in proportion to its component revenues.

In another post regarding the capital structures of other technology companies with different business models I noted that Apple has changed its capital structure to a significant degree over the previous three years.

In the following graph I combined these observations to show how capital expenditure patterns may be used to discern the underlying business model.

That’s just a teaser tidbit. So go straight to the source for the Asymco analysis.  There is a lot going on here that is not obvious.

I consider this extraordinary evidence of an extraordinary shift in strategy.

(…) 

So what tale does this capital tell?

 

iPad mini vs iPad 4 benchmark tests

Mark Hattersley recently wrote a summary of the iPad benchmarks. His Macworld article is a good reference if you are trying to decide which iPad to purchase. Here’s the Geekbench raw CPU results for all iPads:

Mark concludes with this this:

There’s no doubt that the new iPad 4 stomps all over the iPad mini in terms of raw power. Like the recent iPhone 5 and iPod touch update, there’s been a serious performance boost that doubles the capability of the device. What’s not so clear is why? Why has Apple introduced these all-new powerful devices, because there’s currently no particular advantage to the end user. The iOS interface is snappy on all devices, the current generation of games are designed to work on all machines (and our experience in the past is that developers stick with designing for the whole market rather than the latest iOS models for a long time). Perhaps the only advantage is a small performance gain when exporting movies or audio in iMovie or GarageBand.

There’s still a big advantage to getting an iPad 4 over an iPad mini, namely the Retina Display, which is in itself worth the extra money. But don’t think that the iPad mini is less of an experience. It may be smaller, with a smaller screen, and a non Retina display, but it runs all the programs and apps just as well as the recent iPad 3 with Retina Display.

Whether Apple has something planned for the iPad 4 (as well as iPhone 5 and iPod touch) that takes advantage of all that extra power is another matter. The iPad 4 certainly has more future-proofing behind it.

But here and now: they’re both great devices.

Fraser Speirs reports on his iPad Mini experience

Fraser Speirs is perhaps the most knowledgeable IT person regarding heavy use of the iPad in K-12 education. He is responsible for launching and running the iPad 1:1 program at Cedars School of Excellence in Scotland.

Here’s the two posts: Two Weeks with iPad mini and What’s On My iPad Mini. After the first couple of weeks Fraser observed:

The first thing to get out of the way is that the iPad mini is an iPad. Even more than calling it a real iPad, I want to describe it as a full iPad. Give or take a few benchmark points, it’s as powerful as any iPad that existed until the 4th-generation 9.7″ iPad. This is really important. It’s important because the executive summary of what I’m about to write is this: get the one you like best.

(…) That’s when it clicked. When I realised I had – without really thinking – done all the things I need an iPad to do for a whole week without being forced back to a full-size iPad, I saw that the iPad mini is just that: an iPad. No need to over-think the distinction, no real need to develop theories about it: the iPad mini is an iPad in the same way that the 13″ and 15″ MacBook Pro are both Macs. They’ll both do the same 95% of the job: get the one that suits you best.

The iPad mini reminds me of my first MacBook Air. When the Air first shipped it was a Mac with some serious technical compromises with a design and form factor so compelling that you would re-arrange your entire digital life to make it work. The iPad mini reminds me of that except that it only has one serious compromise: the non-retina display. In every other respect, it’s a full-bore iPad. In fact, I don’t even refer to it as “my iPad mini” any more; I just call it “my iPad”.

How Apple and Amazon Security Flaws Led to My Epic Hacking

Don’t let this hack happen to you! 

Meet Mat Honan. He just had his digital life dissolved by hackers. Photo: Ariel Zambelich/Wired. Illustration: Ross Patton/Wired

In the space of one hour, my entire digital life was destroyed. First my Google account was taken over, then deleted. Next my Twitter account was compromised, and used as a platform to broadcast racist and homophobic messages. And worst of all, my AppleID account was broken into, and my hackers used it to remotely erase all of the data on my iPhone, iPad, and MacBook.

The Apple Boycott: Apple quality control vs. This American Life quality control (not)

Economist Joshua Gans does a very nice job of peeling apart the many failings in TAL’s fact-checking. It was a simple Google search that unravelled Daisey’s lies. Why did TAL screw up so badly? Could it be that they really wanted the story to be true? [Ed, that's my speculation, not Prof. Gans].

Like everyone else, I downloaded and listened to This American Life‘s podcast about Mike Daisey, an entertainer, who had produced a show about workers at Apple suppliers in China. When I listened to it, I didn’t hear anything new. These allegations had been around for some time. What I heard was This American Life giving them weight. They are the ‘gold standard’ in journalism much like Apple is the gold standard in design. In both cases, their brand carries credibility. I can take each at face value and, of course, on this issue they clashed.

As everyone knows, Daisey’s story was a fabrication. The best take is it was a dramatic retelling of the existing allegations. The worst take is obvious. To their credit, This American Life devoted an entire episode to their failings and not only retracted the story but covered precisely why. The whole episode will become a textbook case for journalism for years to come. But what I want to focus on here is, why did This American Life fail?

The line by them is that their fact checking process was flawed in just one way. It was flawed because they did not go far beyond Mike Daisey in checking those facts. In particular, the one person who could verify much of the story — Daisey’s interpreter — could apparently not be located. And how did they know that? Daisey told them so. That was a critical link that could have broken the chain and uncovered all this before the story went out. Somewhat embarrassingly, a simple Google search found the interpreter. (Of course, I had to wonder if that was really the right person but I’ll take the reporters’ words for it.) But it wasn’t the only link that was fragile and This American Life did not spell that out. Let me indicate some others.

First, the reason the issues were uncovered is that journalists who report on China and these suppliers were suspicious. So why didn’t TAL ask any of them beforehand what they thought? Some were at public broadcasting. Were they keeping the scoop secret? What happened there? Had they asked, this would have been taken care of.

Second, in the podcast, Apple refused to comment on the story. But Apple could have been key in verifying some of this. This is a difficult issue given they are surely conflicted but just seeing if a corporation wants to comment is not enough. We do not know how pressed Apple were on this.

Third, Daisey claimed to be a huge Apple fan. This is actually one of the most powerful parts of that story. In the retraction, there is nothing about this. It is not hard to check if someone is an Apple fan. There are things they would know and do. What happened there?

(…) There is a remarkable similarity between the tight conditions that generate quality both at TAL and at Apple. Indeed, that should have given TAL special insight but it did not. Instead, their own quality assurance processes failed at multiple points. It wasn’t just one thing. Ironically, it was Apple (and the podcast invention) that brought This American Life to my life (as I did not live in the US). Hopefully, they can learn more from them in the future.

Read the whole thing.

More excellent analysis by Tim Worstall at Forbes.

The Apple Boycott: People Are Spouting Nonsense about Chinese Manufacturing

Tim Worstall at Forbes tackles some of the lies and uninformed rubbish of the daily news cycle. Tim credits the NYT series as being the source of the anguish, but surely a lot of this nonsense derives from the “theater” of the now-discredited Mike Daisey. If you are quoting the execrable Daisey from the This American Life episode then you need to study RETRACTING “MR. DAISEY AND THE APPLE FACTORY”:

Ira (Glass) writes:

I have difficult news. We’ve learned that Mike Daisey’s story about Apple in China – which we broadcast in January – contained significant fabrications. We’re retracting the story because we can’t vouch for its truth. This is not a story we commissioned. It was an excerpt of Mike Daisey’s acclaimed one-man show “The Agony and the Ecstasy of Steve Jobs,” in which he talks about visiting a factory in China that makes iPhones and other Apple products.

The China correspondent for the public radio show Marketplace tracked down the interpreter that Daisey hired when he visited Shenzhen China. The interpreter disputed much of what Daisey has been saying on stage and on our show. On this week’s episode of This American Life, we will devote the entire hour to detailing the errors in “Mr. Daisey Goes to the Apple Factory.”

Daisey lied to me and to This American Life producer Brian Reed during the fact checking we did on the story, before it was broadcast. That doesn’t excuse the fact that we never should’ve put this on the air. In the end, this was our mistake.

We’re horrified to have let something like this onto public radio. Many dedicated reporters and editors – our friends and colleagues – have worked for years to build the reputation for accuracy and integrity that the journalism on public radio enjoys. It’s trusted by so many people for good reason. Our program adheres to the same journalistic standards as the other national shows, and in this case, we did not live up to those standards.

It is shocking how gullible are the producers of This American Life. It seems obvious to me that they wanted to believe Mike Daisey’s emotional story about big bad Apple destroying the lives of underage workers making iPads. So they did not factcheck properly – “the story was so good it must be true”. The only good news is that they are taking some very small responsibility for their mistakes in giving credence to Mike Daisey’s lies. But they take no responsibility for any harm done to the workers at Apple. Not a single word of apology to Apple, Apple workers or Apple shareholders. Not a single word.

Back to Tim Worstall at Forbes:

It would appear that there’s momentum being gained for the idea of boycotting Apple‘s products over conditions in the company’s manufacturing chain in China. This is a very silly idea and there is much nonsense being spouted about those conditions.

Apple, the computer giant whose sleek products have become a mainstay of modern life, is dealing with a public relations disaster and the threat of calls for a boycott of its iPhones and iPads.

The company’s public image took a dive after revelations about working conditions in the factories of some of its network of Chinese suppliers. The allegations, reported at length in the New York Times, build on previous concerns about abuses at firms that Apple uses to make its bestselling computers and phones. Now the dreaded word “boycott” has started to appear in media coverage of its activities.

“Should consumers boycott Apple?” asked a column in the Los Angeles Times as it recounted details of the bad PR fallout.

Two of the New York Times articles are here and here. Dan Lyons weighs in here.

Essentially, the list of charges is that the near 1 million people who work for Foxconn (about 230,000 of whom produce products for Apple, the others assembling for Dell, HP, just about every electronics company in fact) have to work long hours for low pay in dangerous conditions.

Well, yes, they’re poor people living in a poor country. That’s what being poor means, having to work extremely hard to make very little. Yes, that is a harsh thing to say but then reality can indeed be harsh.

To show that it’s not just uncaring neoliberals like myself who say such things why not try reading Paul Krugman on the subject of sweatshops? Specifically, here, on what would happen if we were to try and stop the manufacturing being done in such poor places:

First of all, even if we could assure the workers in Third World export industries of higher wages and better working conditions, this would do nothing for the peasants, day laborers, scavengers, and so on who make up the bulk of these countries’ populations. At best, forcing developing countries to adhere to our labor standards would create a privileged labor aristocracy, leaving the poor majority no better off.

And it might not even do that. The advantages of established First World industries are still formidable. The only reason developing countries have been able to compete with those industries is their ability to offer employers cheap labor. Deny them that ability, and you might well deny them the prospect of continuing industrial growth, even reverse the growth that has been achieved. And since export-oriented growth, for all its injustice, has been a huge boon for the workers in those nations, anything that curtails that growth is very much against their interests. A policy of good jobs in principle, but no jobs in practice, might assuage our consciences, but it is no favor to its alleged beneficiaries.

And a very important point, again from Professor Krugman, about what determines the wages that are paid:

Wages are determined in a national labor market: The basic Ricardian model envisages a single factor, labor, which can move freely between industries. When one tries to talk about trade with laymen, however, one at least sometimes realizes that they do not think about things that way at all. They think about steelworkers, textile workers, and so on; there is no such thing as a national labor market. It does not occur to them that the wages earned in one industry are largely determined by the wages similar workers are earning in other industries. This has several consequences. First, unless it is carefully explained, the standard demonstration of the gains from trade in a Ricardian model — workers can earn more by moving into the industries in which you have a comparative advantage — simply fails to register with lay intellectuals. Their picture is of aircraft workers gaining and textile workers losing, and the idea that it is useful even for the sake of argument to imagine that workers can move from one industry to the other is foreign to them. Second, the link between productivity and wages is thoroughly misunderstood. Non-economists typically think that wages should reflect productivity at the level of the individual company. So if Xerox manages to increase its productivity 20 percent, it should raise the wages it pays by the same amount; if overall manufacturing productivity has risen 30 percent, the real wages of manufacturing workers should have risen 30 percent, even if service productivity has been stagnant; if this doesn’t happen, it is a sign that something has gone wrong. In other words, my criticism of Michael Lind would baffle many non-economists.

Associated with this problem is the misunderstanding of what international trade should do to wage rates. It is a fact that some Bangladeshi apparel factories manage to achieve labor productivity close to half those of comparable installations in the United States, although overall Bangladeshi manufacturing productivity is probably only about 5 percent of the US level. Non-economists find it extremely disturbing and puzzling that wages in those productive factories are only 10 percent of US standards.

Finally, and most importantly, it is not obvious to non-economists that wages are endogenous. Someone like Goldsmith looks at Vietnam and asks, “what would happen if people who work for such low wages manage to achieve Western productivity?” The economist’s answer is, “if they achieve Western productivity, they will be paid Western wages” — as has in fact happened in Japan. But to the non-economist this conclusion is neither natural nor plausible. (And he is likely to offer those Bangladeshi factories as a counterexample, missing the distinction between factory-level and national-level productivity).

I quote at such length because it is an extremely important point. Wages paid to manufacturing workers in China are not determined by the productivity of those specific workers. They are not determined by US wages, by the profits that Apple makes nor even by the good intentions of the creative types that purchase Apple products. They are determined by the wages paid by other jobs in China and that is itself determined by the average level of productivity across the Chinese economy.

But now to the specific complaints that are being made. There are three that are being repeated around the intertubes as being particularly outrageous.

(…)

Tim’s graphic above summarizes some of Tim’s following points. But best to get over to Forbes to read the whole thing which includes all the resource-links that I left out above.

David Pogue on OnLive

OnLive is a remarkable achievement, as David Pogue writes:

You’re probably paying something like $60 a month for high-speed Internet. I’m paying $5 a month, and my connection is 1,000 times faster.

Your iPad can’t play Flash videos on the Web. Mine can.

Your copy of Windows needs constant updating and patching and protection against viruses and spyware. Mine is always clean and always up-to-date.

No, I’m not some kind of smug techno-elitist; you can have all of that, too. All you have to do is sign up for a radical iPad service called OnLive Desktop Plus.

It’s a tiny app — about 5 megabytes. When you open it, you see a standard Windows 7 desktop, right there on your iPad. The full, latest versions of Word, Excel, PowerPoint, Internet Explorer and Adobe Reader are set up and ready to use — no installation, no serial numbers, no pop-up balloons nagging you to update this or that. It may be the least annoying version of Windows you’ve ever used.

That’s pretty impressive — but not as impressive as what’s going on behind the scenes. The PC that’s driving your iPad Windows experience is, in fact, a “farm” of computers at one of three data centers thousands of miles away. Every time you tap the screen, scroll a list or type on the on-screen keyboard, you’re sending signals to those distant computers. The screen image is blasted back to your iPad with astonishingly little lag.

There’s an insane amount of technology behind this stunt — 10 years in the making, according to the company’s founder. (He’s a veteran of Apple’s original QuickTime team and Microsoft’s WebTV and Xbox teams.) OnLive Desktop builds on the company’s original business, a service that lets gamers play high-horsepower video games on Macs or low-powered Windows computers like netbooks.

(…)

OnLive says that its service works great over 4G cellular connections (like the one provided by an LTE MiFi) — but 3G connections and feeble hotel Wi-Fi hot spots are too slow to be satisfying. OnLive wants at least a 2-megabits-a-second connection on your end.

Finally, you have to sign into OnLive every time you want to use it, even if you’ve just flicked away to another iPad app. (OnLive says it’ll fix that.)

Even so, if ever there were a poster child for the potential of cloud computing, OnLive is it. This is jaw-dropping, extremely polished technology. It opens up a universe of software and horsepower that live far beyond the iPad’s wildest dreams — with no more effort on your part than a few taps on glass.

Do read the whole thing »



Follow

Get every new post delivered to your Inbox.

Join 201 other followers