Steve Jobs to Headline iPhone-Centric Apple Developer Conference

jobs

Apple this morning announced that CEO Steve Jobs will be emceeing the company’s annual Worldwide Developers Conference keynote on June 7 in San Francisco.

Continuing his trend of doing one-to-one e-mail marketing for his $43 billion (revenue) company, Jobs himself helped tout the conference with a personal e-mail to a customer over the weekend.

The developer’s conference attracts greater than usual attention because, for the past two years, Apple has used the venue to announce the latest version of its iPhone. Gizmodo may have spoiled the surprise this year by leaking what has been confirmed by Apple legal as a prototype of the fourth-generation iPhone. However, in an e-mail exchange with a customer over the weekend, Jobs said the event would still pack a punch.

“I hope you have some good WWDC announcements to blow [Google] out of the water,” a customer wrote to Jobs on Saturday.

“You won’t be disappointed,” the CEO responded, according to a report published on MacRumors.com.

As usual, the keynote address will be held in the Moscone West conference center to kick off the five-day WWDC conference, which includes hands-on sessions for software developers to become familiar with iPhone OS 4 and Mac OS X.

In addition to new iPhone hardware, Apple is expected to give further details on its next-generation mobile operating system, iPhone OS 4. The company in March previewed iPhone OS 4, which introduces support for multitasking and the ability to group apps in folders, among other features.

Apple’s 5,000-seat WWDC 2010 event sold out in eight days. The conference is designed to recruit and educate developers supporting Apple’s iPhone OS and Mac OS platforms.

The importance of WWDC continues to increase as Apple’s rivalry with Google becomes more fierce in the mobile space. Google last week held its sold-out Android developer conference, Google I/O, where executives spent a generous amount of time delivering potshots on Apple’s iPhone platform.

“If Google didn’t act, we face a draconian future. One man, one company, one device would control our future,” Vic Gundotra, vice president of engineering of Google, told attendees at the conference. “If you believe in openness and choice, welcome to Android.”

See Also:

Photo: Jim Merithew/Wired.com


Steve Jobs will be front and center at WWDC 2010 for keynote duties

Just in case you were wondering if Steve Jobs would manage to show up to WWDC 2010 and totally party on the Apple faithful… yes. As you would expect, Steve will be rocking the keynote address on Monday, June 7th at 10AM Pacific. Afterwards you’ll be wondering where you’re going to find the money for that new iPhone. Full PR after the break.

Continue reading Steve Jobs will be front and center at WWDC 2010 for keynote duties

Steve Jobs will be front and center at WWDC 2010 for keynote duties originally appeared on Engadget on Mon, 24 May 2010 08:41:00 EDT. Please see our terms for use of feeds.

Permalink   |   | Email this | Comments

Interface Expert Knocks iPad Apps for Inconsistent Usability

ipadrelease277

The iPad has been hailed as an interface triumph. But one usability expert has published an exhaustive critique of the iPad, taking it to task for the inconsistency and obscurity of its apps’ interfaces.

The problem, at its core: A lack of interface standards means every app behaves in a different way.

Dr. Jakob Nielsen, hailed by some as “the king of usability,” this week published a 93-page report evaluating the iPad’s usability based on feedback from seven users who tested 34 different apps and websites. Because the iPad user interface is new and design standards have not been defined for tablet software, Nielsen argues that iPad apps currently suffer from inconsistency and poor “discoverability.”

“What did I just touch? What did I just do? The way you touch can impact what happens, and you can’t see what you just did, so it’s invisible,” Nielsen said in a phone interview with Wired.com.

Nielsen is criticizing exactly what Wired hailed a few weeks ago: The minimalist interface of the iPad. Because the interface is so sparse, that allows content to take over the entire device — a powerful attraction for content creators and consumers. But, Nielsen says, that can lead to confusion, because it’s hard to tell what you’re supposed to do with what’s onscreen.

“These things accumulate,” he added. “You can’t tell a difference — can you scroll? Will it jump? It makes it more confusing. Here’s the kicker: All these things will be stuff you can actually learn if you put your mind to it. But each application is different and that means this learning will not take place.”

Such is the consequence of abandoning old standards and starting with a clean slate. Over the last 25 years, designers have established and refined a firm set of guidelines for interface design on desktop-based platforms such as the Mac and Windows. Many of those guidelines are baked into operating systems in the form of user interface controls and functions, like scroll bars and radio buttons. But with the emergence of the nearly buttonless, multitouch iPad, Apple has unleashed a new beast.

Even Apple hasn’t seemed to have nailed a standard yet for the iPad. According to Daring Fireball blogger John Gruber, Apple scrapped some of its default iPhone software — the clock, calculator, stocks, weather and voice apps — because they didn’t look right when re-purposed for the iPad.

“Ends up that just blowing up iPhone apps to fill the iPad screen looks and feels weird, even if you use higher-resolution graphics so that nothing looks pixelated,” Gruber wrote. “It wasn’t a technical problem, it was a design problem.”

On top of that, developers of the first iPad apps did not have possession of iPads prior to launch. Thus, the majority of early iPad apps were basically coded in the dark, which is why interfaces are varying so wildly, Nielsen said.

“Apple should get some hard whacks over the head for that,” Nielsen said. “It’s not that the developers or designers can’t do it; it’s just that they weren’t allowed to do it.”

In the summary of his study, Nielsen listed examples where touching a picture caused apps to behave in five different ways: Nothing happens, the picture enlarges, the picture links to additional information, the image flips to reveal more photos, or navigation choices pop up.

Nielsen also knocked content-based iPad apps for having a “crushing print metaphor.” That is, content often lacked the basic interactivity of a web page, and for most content apps you can’t tap a headline to jump to a corresponding article.

Nielsen stressed that this was only an early study, and he’s aware designers are still devising a set of standards for iPad apps. He said the purpose of publishing his study now was to point the problems out to developers early so they can begin discussing solutions and achieve consistency.

“One reason we published this now is I don’t want months to go by with thousands of other wacky apps coming out,” Nielsen said. “I want these designers thinking, ‘Let’s worry about this now,’ so we can come to a consensus about best practices.”

tumblr_kz19pxppv41qz4rgrAlready, some iPad app developers are opining in blogs and forums about iPad design principles. For example, Marco Arment, developer of the popular iPhone and iPad app Instapaper Pro, wrote a blog post about overdoing interface metaphor — designing software to appear too similarly to the physical object it’s trying to reproduce.

The problem with that approach, Arment argued, is that nearly every limitation and frustration of the original physical object has also been reproduced. The app version of a calculator, for example, hasn’t made any significant advancements from the physical object, and in some ways the real thing is still better.

Arment explained that his “read later” app Instapaper Pro was an example of software that breaks free from metaphor. In reading mode, you can view articles that split up into easily readable “cards,” but as soon as text is selected, you can begin scrolling. In that way, it’s a combination of the experience of reading a website and a book.

Nielsen’s study did cover the dilemma developers face between cards and scrolling for reading content, echoing many of Arment’s thoughts.

“I read that Nielsen post and loved it,” Arment told Wired.com. “It confirms a lot of what I’ve been thinking with iPad interfaces.”

“Developers are particularly challenged to make touch interfaces discoverable while preserving attractiveness and minimizing clutter,” he added. “If everything touchable clearly looks like a button, we won’t win any design awards. But if everything looks pretty and features are buried by too many images and textures, a lot of our customers won’t find important functionality.”

See Also:

Photo: Brian Derballa/Wired.com


5 Things Apple Must Do to Look Less Evil


It’s appropriate that the Apple logo on the iPad is black. The Cupertino, California, company’s image is taking on some awfully sinister tones lately.

For a company that made its name fighting for the little guy, it’s a surprising reversal. In the past, Apple touted itself as the computer company for nonconformists who “Think Different.” Now the company is making moves that make it look like the Big Brother it once mocked.

First Apple tightened its iron grip on the already-stringent iPhone developer policy, requiring apps to be made with Apple-approved languages, which disturbed some coders and even children. A short while later, Apple rejected some high-profile apps based on their editorial content, raising journalists’ questions about press freedoms in the App Store. Then, police kicked down a Gizmodo editor’s door to investigate a lost iPhone prototype that Apple had reported as stolen. Even Ellen DeGeneres and Jon Stewart have mocked Apple’s heavy-handed moves.

Plenty of us love our shiny iPads, iPods, iPhones and MacBooks — state-of-the-art gadgets with undeniable allure. But it’s tough to imagine customers will stay loyal to a company whose image and actions are increasingly nefarious. We want to like the corporation we give money to, don’t we?

Here are five things Apple should do to redeem its fast-fading public image.

Publish App Store Rules

As I’ve argued before, the App Store’s biggest problem is not that there are rules, but that app creators don’t know what the rules are. As a result, people eager to participate in the App Store censor themselves, and that hurts innovation and encourages conformity. The least Apple can do is publish a list of guidelines about what types of content are allowed in the App Store. After all, Apple has had nearly two years and almost 200,000 apps to figure out what it wants in the App Store. Tell people what the rules are so they know what they’re getting into, and so they can innovate as much as possible. That would also tell us customers what we’re not getting on our iPhone OS devices.

Formalize Relationships With Publishers

Publishers are hypnotized by imaginary dollar signs when they look at the iPad as a platform that could reinvent publishing and reverse declining revenues. But after recent editorial-related app rejections, journalists are slowly waking up to our forewarning that Apple could control the press because news and magazine apps on the iPad are at the mercy of the notoriously temperamental App Store reviewers. If Apple wants to look a little less like the Chinese government, it should work with publishers to ink formal agreements regarding content to guarantee editorial freedom to respected brands.

Tweak iPhone Developer Agreement

Apple’s stated purpose of its revised iPhone developer policy is to block out meta platforms to ensure a high level of quality in the App Store. Also, from a business perspective, there is no lock-in advantage if you can get the same apps on the iPhone as you can on other competing smartphones. Fair enough, but Apple would be silly to think it can keep the mobile market all to itself, and its developer agreement comes off as a piece of literature holding developers hostage.

It’s hard to create new rules, but it’s easy to abolish existing ones. Apple should loosen up its iPhone developer agreement by snipping out a part of section 7.2, which states that any applications developed using Apple’s SDK may only be publicly distributed through the App Store. That implies that if you originally create an app with the Apple SDK, you’re not allowed to even modify it with different languages and sell it through another app store like Google’s Android market. In other words, iPhone apps belong to Apple. This rule is basically unenforceable to begin with, and Apple should just remove it, along with other similar policies.

Apologize to Jason Chen

Reasonable people can disagree over whether it was ethical for Gizmodo to purchase the lost iPhone prototype, but the police action — kicking down Jason Chen’s door to seize his computers — was overboard. It was self-evidently a clumsy move: After damaging Chen’s property, the police paused the investigation to study whether the journalists’ Shield Law protected Chen. The proper action would have been to issue a subpoena to get Chen to talk about the device first. Apple, which instigated the police action by filing a stolen property complaint, should publicly apologize to Chen (no relation to the author of this post) and reimburse him for the damages.

Get Gray Powell on Stage

When Apple accidentally leaked its PowerMac G5 a couple of years ago, Apple’s legal team forced MacRumors’ Arnold Kim to pull down his post containing the information. But a humbled Steve Jobs joked about the slip during his WWDC 2003 keynote, calling it a case of “Premature specification.” (See the video below.)

He should do a similar thing when he officially unveils Apple’s next phone, by having Gray Powell — the engineer who misplaced the next-generation iPhone prototype — make a stage appearance. Powell could walk out and hand Jobs the phone, saying “Hey Steve, I found your lost phone,” or something similar. Some comedic relief, provided by the engineer who lost the iPhone prototype in a bar, can remind us that Apple is still a company guided by a man with a sense of humor.

See Also:


MS releases new Windows Phone 7 dev tools, we take ’em for a spin and you can too (video)

Windows Phone 7 developers get a new release, we take for a spin, and you can too! (video)MS releases new Windows Phone 7 dev tools, we take 'em for a spin and you can too (video)

Hey, remember how Microsoft released a very limited version of the Windows Phone 7 binaries for developers, and then it took about 34 seconds for someone to unlock them to open up all their hidden goodness? Well, MS has just the delivered an updated set of tools for developers to help them get a little closer to making millions on the Maketplace, and yet again it took no time at all for that release to be unlocked This time there are a few new goodies to take a look at and if you’d like to take a peek, and learn how to try them out for yourself, click on through.

Continue reading MS releases new Windows Phone 7 dev tools, we take ’em for a spin and you can too (video)

Filed under:

MS releases new Windows Phone 7 dev tools, we take ’em for a spin and you can too (video) originally appeared on Engadget on Sun, 02 May 2010 12:12:00 EST. Please see our terms for use of feeds.

Permalink   |  sourceThe Windows Blog, xda-developers forum  | Email this | Comments

A Call for Transparency in Apple’s App Store

ipadrelease0091

The iTunes App Store is nearly two years old, and Apple still has not published a clear set of guidelines about what type of content is and isn’t allowed inside apps. That’s a problem, especially for publishers eying the iPad as a potential platform for the future of publishing, and it’s an even bigger problem for readers.


We in the press don’t know to what extent we can retain our editorial freedom in the App Store. Working with Apple’s current opaque policy, we’re left to trust that Apple will do the right thing. And time and time again, Apple’s App Store reviewers have been proven fallible, as recently shown by the rejection of Mark Fiore’s Pulitzer-winning cartoon. Apple rejected the toon because it “ridicules public figures,” and after coming under fire in the press, the company approved the app. But in reversing its decision, Apple still did not make its content policy clear.

Instead, the Fiore episode raised more questions. Does it mean we can now publish satire? Or does it mean we have to win a Pulitzer in order to publish satire? Or does it mean we have to stir up negative press in order to publish satire?

The fact there are so many questions points to a paramount concern: Readers don’t know what they could be missing when they’re reading the iPad edition of a publication, as opposed to its print or web version.

The issue is poised to grow as more iPads sell. To understand, you have to consider the logistics of embracing a new publishing medium such as the iPad. Media operations must integrate digital tablet production into their infrastructure, and it’s neither easy nor inexpensive to obtain the software developers, designers and content creators to make such a transition. And if advertisers invest more money in the iPad version of a publication, that pressures publishers to give priority to resources allocated to the iPad.

Given Apple’s lead in mobile, the rate at which Apple and the App Store are growing and the wild enthusiasm among advertisers lining up for the iPad opportunity, it seems inevitable that Apple will to some extent have influence over the content that publishers produce.

Tech observers have correctly compared the App Store to Walmart, which refuses to sell musical albums carrying the Parental Advisory tag. Walmart has even suggested that artists change lyrics and CD covers it deems objectionable. Given the retail chain’s position as the world’s largest music retailer, many agree Walmart has altered the way the recording industry creates albums.

The major difference between the App Store and Walmart, however, is that the RIAA has published details about the Parental Advisory program. Apple has not published such documents regarding content for apps.

Following the Fiore incident, the journalism industry is slowly waking up to my forewarning published in February about the potential for Apple to take control of the press. The Association of American Editorial Cartoons published a letter on April 22 asking for Apple to support free speech.

“The Association of American Editorial Cartoonists calls on Apple to immediately stop rejecting apps because they ‘ridicule public figures’ and are deemed ‘objectionable,’” the association wrote. “Now is the time for Apple to welcome a vibrant and diverse world of news and opinion with open arms.”

Columbia Journalism Review’s Ryan Chittum expressed his concerns about the rejection in his editorial “It’s time for the press to push back against Apple.

“If the press is ceding gatekeeper status, even if it’s only nominally, over its speech, then it is making a dangerous mistake,” wrote Chittum. He makes an extreme suggestion: Yank apps from the store until Apple agrees to give publishers complete control over their content.

I partly disagree: A strong argument for Apple’s tight control is the level of quality and protection provided by its App Store — an experience many customers enjoy. My position is more moderate: It’s OK for there to be rules required for us to play in the App Store. It’s just not OK that publications and their readers don’t know what the rules are. As advocates of transparency, we in the press should demand transparency from our new partner, Apple.

Make no mistake, though written from the perspective of a Wired writer, this editorial doesn’t just concern the press. Everybody participating in the App Store is a part of “new media” and should be demanding that Apple come clean with its rules.

If there’s anything valuable we can extract from South Park’s last-minute censorship of Mohammed in response to a death threat from a Muslim website, it’s that capricious censorship bears unexpected consequences. Similar can be said about Apple. In a creative platform like the App Store, when censorship is imposed without making clear what the rules for censorship are, the natural reaction for eager participants is to over-censor themselves so as not to be punished. That’s bad for innovation and democracy, and the detrimental side effect is widespread conformity — ironic, coming from a company whose former slogan was “Think Different.”

Brian X. Chen is writing a book examining the positive and negative implications of the iPhone revolution, scheduled to publish Spring 2011 by Perseus Books Group.

Updated 7:30 a.m. PT: Posted a link to the letter published by the Association of American Editorial Cartoonists.

See Also:

Photo: Bryan Derballa/Wired.com


Apple Technical Note TN2267: an opening for GPU-accelerated Flash?

There couldn’t possibly be any less fanfare from Apple on this, but the company’s recently released Technical Note TN2267 for OS X 10.6.3 might just be the GPU-sized opening that Adobe and, consequently, Flash users have been waiting for. Here’s the key bit:

The Video Decode Acceleration framework is a C programming interface providing low-level access to the H.264 decoding capabilities of compatible GPUs such as the NVIDIA GeForce 9400M, GeForce 320M or GeForce GT 330M. It is intended for use by advanced developers who specifically need hardware accelerated decode of video frames.

Now, we’re not exactly “advanced developers,” but it seems pretty clear that this is designed to give developers access to some inner workings of OS X that have previously been restricted to Apple itself — access that has been evident in Flash tests that show it performs much better in instances where it can access a computer’s GPU. No word from Adobe on this just yet, but we’ve got to guess they’ve already taken notice.

Apple Technical Note TN2267: an opening for GPU-accelerated Flash? originally appeared on Engadget on Thu, 22 Apr 2010 14:32:00 EST. Please see our terms for use of feeds.

Permalink Daring Fireball  |  sourceApple  | Email this | Comments

Adobe Gives Up on Flash for iPhone, iPad

flashiphone

Adobe will no longer pursue its plans to bring Flash to Apple’s iPhone and the iPad.

Adobe on Tuesday evening said it is ceasing investment in a software tool that enables Flash developers to port software into native iPhone and iPad apps, according to Mike Chambers, Adobe’s principal product manager for Flash developer relations.

“The primary goal of Flash has always been to enable cross-browser, platform and device development,” Chambers wrote in a blog post. “This is the exact opposite of what Apple wants. They want to tie developers down to their platform, and restrict their options to make it difficult for developers to target other platforms.”

Adobe is reacting to a new rule in the iPhone developer agreement, which stipulates that iPhone and iPad apps must be coded with Apple-approved programming languages, such as C++ or Objective C. If enforced, the rule would effectively ban any apps coded with Adobe’s Packager for iPhone, a tool enabling Flash-coded software to be easily converted into native iPhone apps, released last week with Adobe CS5.

Faced with Apple’s new rule, Adobe pulled the plug on Packager for iPhone. That ends, for now, any hope that Flash apps (or apps that incorporate Flash) will ever be able to run on the iPad or iPhone.

Apple’s new app policy has been met with furious debate. Critics say Apple is depriving consumers of choice, because Flash apps that could have been on the iPhone will never see the light of day. Supporters of Apple’s decision, including Steve Jobs, say the move was necessary to retain quality of apps in the App Store and nimbleness of updating the platform.

Apple has been steadfast with its lack of support for Flash on the iPhone OS. Some customers have complained that without Flash, iPhone and iPad users are missing out on a big chunk of the internet. Jobs said during a staff meeting that Flash was not supported because it is “buggy” and frequently causes crashes on the Mac OS, according to a secondhand account first reported by Wired.com.

Rather than supporting Flash, Apple has reportedly pushed website creators to use alternative web standards, including HTML5, CSS and JavaScript, which are all supported by the iPhone and iPad browser.

Apple said Adobe was incorrect to accuse Apple of locking in developers by not supporting Flash.

“Someone has it backwards — it is HTML5, CSS, JavaScript and H.264 (all supported by the iPhone and iPad) that are open and standard, while Adobe’s Flash is closed and proprietary,” an Apple representative said in a statement provided to CNET.

However, as simple as it may sound for web developers to switch to different standards, Wired.com’s Webmonkey editor Mike Calore said the transition to HTML5 for video playback would be complex. He explained that there’s no agreed upon video format for HTML5, and support varies greatly from browser to browser.

“Not to be overly critical of Apple — anyone pushing for open web standards deserves kudos — but the company seems more deeply concerned with digging Flash’s grave than it does with promoting semantic markup,” Calore wrote.

See Also:



Adobe halts investment in iPhone-specific Flash dev tools, has another dig at Apple (update: Apple responds)

Color us unsurprised, but it’s still notable to hear that Adobe is stopping investment in its software’s capability to port content over to iPhone OS. The company’s great hope on this front, Packager for iPhone, will still ship as part of Flash CS5 as planned, but beyond that Adobe is essentially giving up on Apple’s mobile OS until further notice. In spite of being repeatedly rebuffed by Jobs and company before, the Flash maker had kept up hope that it could sway (or nag) Apple into validating its wares, but the final straw in this relationship seems to have been Apple’s dev tool lockdown. So what will Adobe do now? Principal Product Manager Mike Chambers tells us that Android is doing kind of okay and his company will shift its attentions to it and other mobile platforms. Of course, we’re just giving you the cleaned up version — for the full finger-pointing diatribe against Apple, you’ll have to hit the source link.

Update: Right on cue, here’s Apple’s terse response: “Someone has it backwards–it is HTML5, CSS, JavaScript, and H.264 (all supported by the iPhone and iPad) that are open and standard, while Adobe’s Flash is closed and proprietary.”

Adobe halts investment in iPhone-specific Flash dev tools, has another dig at Apple (update: Apple responds) originally appeared on Engadget on Wed, 21 Apr 2010 03:25:00 EST. Please see our terms for use of feeds.

Permalink Loop Insight  |  sourceMike Chambers  | Email this | Comments

iPhone OS 4 jailbreak released to developers, not you

Be clear on this: if you’re not a jailbreak app developer then the redsn0w 0.9.5 beta release is not for you. The iPhone OS 4 jailbreak previously hinted at is for real and it’s for devs only so that they can prep their wares for the summer update. Don’t worry, it doesn’t reveal anything new to Apple and no, it won’t work on the iPad — it’s Mac OSX only, iPhone 3G only, and iPhone 4.0 beta 1 only for now. But hey, it’s early days, at least you know it’s out there and that people smarter than you are tending to things.

iPhone OS 4 jailbreak released to developers, not you originally appeared on Engadget on Fri, 16 Apr 2010 01:06:00 EST. Please see our terms for use of feeds.

Permalink 9to5 Mac, @MuscleNerd (Twitter)  |  sourceiphwn  | Email this | Comments