macstoriestaff

– 5 posts on MacStories

http://www.macstories.net/ – @

Editor’s Note: This is a guest post by Ken Yarmosh, the creator of the popular iOS apps Agenda Calendar and Buzz Contacts. Read more about him at his blog and follow him on Twitter.

With the announcement of “the new iPad,” developers are quickly readying their apps for the latest and greatest iOS device from Apple. Preparing an iOS app for a more powerful, Retina display device is a familiar task for those developers who got apps ready for the iPhone 4. Whether you do or don’t have that experience, it’s still helpful to have a checklist of sorts for preparing your app for the new iPad.

Here’s that list.

Download the Latest Version of Xcode

Before you get too excited, open up the Mac App Store to download Xcode 4.3.1. This will provide you with the “iPad (Retina)” simulator and the ability to build against the iOS 5.1 SDK. Even though an iOS 5.0.x iPad app will run on the new iPad (or any iPad running iOS 5.1), remember that the new iPad will ship with iOS 5.1. So, building against the proper SDK is always a smart choice.

Update Designs Assets for Retina display

Getting your UI assets updated for the new iPad’s Retina display should be relatively straightforward. Hopefully, you’ve built your application in a way that will mostly make it a design-related task of scaling up your images and applying the “@2x” designation to them. This can be slightly more involved than what was required for the iPhone 4 Retina display update because of the importance of both portrait and landscape on the iPad. Don’t forget to update your “Launch Images” for both orientations, as well as your “App Icons.” If you want more specifics on this topic, see the Apple-related documentation or read Marc Edwards’ post on designing for Retina display on the Bjango site.

Test in iPad (Retina) iOS Simulator

If you want your iPad app looking shiny the day the new iPad arrives, you’ll be stuck trying to use the ginormous iPad (Retina) simulator since the new iPad isn’t available now. Even on Apple’s 27-inch Thunderbolt or Apple Cinema Display, you’ll be struggling to view your app in portrait and barely be able to see it in landscape. Use the window scale and adjust it to 75% or 50% accordingly.

Check Wi-Fi Download Limit

Paul Haddad of Tapbots reported Tweetbot for iPad going from 8.8MB to 24.6MB post-Retina display upsizing. Since many iPad apps are content-intensive, definitely keep tabs on the total size of your app. Even with the new 50MB Wi-Fi download limit, Retina display assets will add up quickly.

Consider New Features

Should you be readying your app for the new iPad on launch day, you’re probably not going to add many new features to your app. But the new iPad does come with more than just Retina display, including the much faster A5X processor, a new camera, dictation (which is available to third-party apps), LTE, and Bluetooth 4.0. Think about how these new features can impact your app and consider how your app might be made better by specifically using them.

Submit to Apple

Apple is now asking developers to submit apps updated for iOS 5.1, including apps optimized for the new iPad. So, once you’ve gone through the steps above, submit to Apple and hurry up and wait. Make sure you mention in your “What’s New” release notes, as well as your version-specific App Store description that your app is now iOS 5.1 tested and Retina display ready. You’re not done yet though!

On-Device Testing

When you get that new iPad in your hands, the first thing you should do is open up your app. Do some pixel nitpicking and ensure everything is working as expected. Faster devices may cause certain parts of the user interface to load faster than others, can handle content pulled in from APIs to process differently, and more generally, may require some small tweaking.
iPad hero

Re-Submit to Apple

If you found issues during the on-device testing, prepare another update and once again, submit your iPad app to Apple. If any crashing or critical bugs were identified during on-device testing, consider (very carefully) requesting an expedited review.

Congratulations, you’re ready for the new iPad. Here’s to 25 billion more app downloads and many five star App Store reviews.

At 10 AM tomorrow, Apple will begin the presentation of one of the most (if not the most) anticipated products in the company’s recent history: the iPad 3. Rumored to feature a Retina Display, improved graphics, and a better camera, the next iPad will have to build on the amazing success of the iPad 2 (where by “amazing” we mean “just look at those numbers“) whilst giving owners of the original iPad a reason to upgrade after two years. And with the possible implications behind the rumored new features, it looks like those who stood in line back in April 2010 will have more than one good reason to consider the Next Big Thing.

As a team, we typically refrain from reporting every single rumor that shows up ahead of an Apple product release, leaving our crystal ball and teardrop-shaped hats under the editorial desk. Having considered the variables behind a Retina iPad 3 in the past, however, we couldn’t resist this time — much like we did back at WWDC ’11, we had to get together (in a cozy Campfire) and share our March 7th Apple Event predictions. Our own Gabe Glick already explained why he thinks a big announcement will be about software — specifically, he neatly illustrated why Aperture may be coming to iOS and the iPad 3. Below, you can follow the rest of the MacStories team as we reflect on what we think has to happen, what could happen, and what we generally would like to see in a Retina-enabled tablet future. Lots of coffee may or may not have been involved in the editing process of said predictions — pardon the excitement, but we think the next iPad is going to be a fantastic upgrade.

After the break, you’ll find our predictions. We will check back on these later this week, and make sure to tune in on MacStories’ homepage tomorrow for our complete coverage. (more…)

At MacStories, we strive to produce great content every day. From news to stories and app reviews, we care about quality content to deliver to you, our readers, with insight and our personal analysis every day. But we can’t cover everything. And there’s some great writing on the Internet that we often can’t link to in our daily coverage, if only because there isn’t much we can add to an already excellent article.

Today we are introducing MacStories Reading List, a weekly selection of great stories from Authors that you should read. Every Sunday, we’ll publish a collection of links that we think you should read, such as the ones below. A very simple format for the great writing that is happening in the Apple community.

Even better, you can subscribe to the Reading List in your favorite RSS reader or Instapaper. We have created an Instapaper account dedicated to the Reading List, so head over this link to get the Instapaper feed for the links we’ll post here every week. You’ll also be able to able to find us in Instapaper if you’re already following @macstoriesnet and linked the service to your Twitter account.

On behalf of the entire MacStories team, I wish you a good reading. – Federico Viticci

World of Apple’s Alex Brooks reflects on his past few years of blogging, and ultimately decides that quality content, not the page views alone, is what matters. A must-read.

The site I want to read and will produce will post thoughtful commentary on Apple. The kind of commentary and prose that that’s sensible, articulate and adds value to a wider discussion happening across the internet. There are already a handful of sites just like this, authors who have in some cases taken grave risk to quit their day to day lives to produce content just like this. I value those sites, I enjoy reading their content.

Reflecting on Change, Alex Brooks (@alexbrooks)

Every month or so an analyst comes out and claims the iPad can’t be included in the same market share numbers of PCs, and vice versa. Asymco’s Horace Dediu collects actual numbers and puts things in perspective, revealing the true effect Android and iOS devices are having on the PC market.

This last view corresponds to the data in the first graph (line chart). If iOS and Android are added as potential substitutions for personal computing, the share of PCs suddenly collapses to less than 50%. It also suggests much more collapse to come.

- The rise and fall of personal computing, Horace Dediu (@asymco)

How has the App Store third-party ecosystem evolved in the past four years? Is there still much of a difference between smaller developers who actually want to charge for their apps, and bigger studios that have adopted the “freemium” or in-app advertising models? App Cubby’s David Barnard has an insightful article from an indie developer’s perspective that’s worth reading and reflecting upon.

Ultimately, the users become the product, not the app. Selling users to advertisers and pushing in-app upgrades/consumables is a completely different game than carefully crafting apps to maximize user value/entertainment. It’d be a shame if the mobile software industry devolved into some horrific hybrid of Zynga and Facebook.

Free and Low-Cost Apps, David Barnard (@drbarnard)

Wandering Coder’s Pierre Lebeaupin makes an excellent case for iOS needing some sort of file management system at this point. You can disagree with him, but it’s undeniable the majority of users who want to use iPhones and iPads in a professional environment are still working with documents, and iOS doesn’t offer a native, integrated way for easily managing and searching them.

Let us contrast that with another situation. My father is a high school teacher; for the last 20+ years he has been working using computers, preparing teaching notes, transparent slides to project, diagrams, tests and their answers, student average note calculation documents, etc. on his Macs (and before that on an Apple ][e). He shares some of these with his colleagues (and back) and sometimes prints on school printers so it’s not like he is working in complete isolation, but he cannot rely on a supporting infrastructure and has to ensure and organize storage of these teaching material documents himself. He will often need to update these when it’s time to teach the same subject one year later, because the test needs to be changed so that it’s not the exact same as last year, because the curriculum is changing this year, because the actual class experience of using them the previous year led him to think of improvements to make the explanation clearer, because this year he’s teaching a class with a different option so they have less hours of his course (but the same curriculum…), etc. Can you imagine him using solely an iPad, or even solely an imaginary iOS 5 notebook, to do so? I can’t.

- iOS lacks a document filing system, Pierre Lebeaupin (@wanderingcoder)

An amazingly detailed and in-depth overview of the iOS gaming scene with a series of post-mortems and sales figures for “blockbuster” and smaller iOS games. If you only read one article about mobile gaming this week, make it this one.

Eighteen months ago, when I left Ubisoft to start an independent game studio and focus on making my own games, I looked online a bit to get an idea of how much income I could expect to make as an indie. At Ubisoft I used to work on big AAA console games, and I had some figures in mind, but I knew they wouldn’t be relevant for my new life: $20M budgets, teams of 200 hundred people, 3 million sales at $70 per unit… I knew being an indie developer would be completely different, but I had very little information about how different it would be.

Angry Birds had taken off, Plants vs. Zombies was already a model, Doodle Jump was a good example of success, and soon after I started my “indie” life, Cut the Rope was selling a million copies a week. But except for what I call the “jackpots,” there were very few public stories or numbers on the web, and this meant we were a bit in the dark when we started SQUIDS. I have been tracking figures since then, and I’m writing this article to share what I’ve learned with my fellow indie dev buddies who might be in the same position I was, a year and a half ago.

- Money And The App Store: A Few Figures That Might Help An Indie Developer, Emeric Thoa

Dov Frankel explains how the iPhone’s mute switch and audio controls really work.

On the last episode of The Talk Show, Gruber and Dan Benjamin discussed the design tradeoffs at length. During the discussion, they mentioned that you can set the iPad’s volume level to 0, but you can’t with the volume buttons on the iPhone. I understand the difference, and it’s something it took me a little while to figure out, way back in the early days of the first-generation iPhone.

- Different Levels, Dov Frankel (@MrDov)

Last week, Apple unveiled its iBooks Textbooks project as the result of deals with major US publishers that have agreed to release digital versions of their textbooks in a new iBooks format. Brian Lam has an interesting interview with former Apple intern Joseph Peters, who might have fueled Apple’s interest in textbooks back in 2008.

In 2008, Apple had its iContest in its Town Hall building. The iContest is sort of an American Idol for great ideas that gives interns a chance to present their best thoughts to executives. Here, Joseph Peters and some friends outlined the idea of bringing Textbooks to iTunes, before the iPad even existed to the rest of us. They won a set of Macbook Airs for their idea.

- Open-Mindedness, Brian Lam (@blam)

Much has been said and written about Apple’s decision to make iBooks Author a proprietary file format that only allows for selling eBooks into the iBookstore. Daring Fireball’s John Gruber looks at the “issue” from Apple’s perspective.

Glazman looks at these new iBooks books and sees a nonstandard proprietary format. Apple looks at these new iBooks and sees layouts and design features that no other e-book platform offers today. One man’s nonstandard is another man’s competitive differentiation.

- On the Proprietary Nature of the iBooks Author File Format, John Gruber (@gruber)

Egg Freckles’ Thomas Brand looks back at Apple’s platform history and how the company has built its success on directly controlling the user experience in every possible way, from content sources to delivering software to the end user.

The iPhone may have been destined to become the world’s most popular smartphone due to the amazing multitouch technology it introduced, but Apple’s control over the iOS operating system, Xcode developer environment, and App Store distribution model have made the iPhone the central member of a new application ecosystem that can’t be beat.

Yesterday’s introduction of iBooks 2 and iBooks Author were significant announcements because they complete the platform pyramid Apple needs to enter the Textbook Market with the same control as its previous successes.

- The iBooks Platform, Thomas Brand (@ThomasBrand)

Macworld’s Serenity Caldwell follows up on Apple’s iBooks Author announcements and notes how authors welcome Apple’s entry in the digital publishing industry, but are still looking forward to a broader ePub-compatible publishing tool with advanced features, a polished interface, and Apple’s refined user experience.

It’s crazy that we have so few options after five years: The ebooks market is clearly making money. If Apple’s release of an authoring tool has shown anything, it’s that the demand is certainly out there. The publishing industry needs a Dreamweaver or Hype-type ePub application—one that won’t be limited by EULAs, or insistent on proprietary formats.

I’ve already written a wish-list for my perfect app; had I the talent, the skills, and the time to build it, I’d be half-tempted to try coding it myself. Silly, of course, but when it comes down to it, I just want to be able to make awesome ebooks. It shouldn’t take two weeks and six programs to create a book with images and interactive content.

- Holding out for an ePub hero, Serenity Caldwell (@settern)

Fraser Speirs, who knows a thing or two about iPad in schools, thinks that textbooks aren’t necessarily the future, but a way to get there.

Apple already revolutionized education when it invented the iPad. While iBooks textbooks are a bridge from the past to the future—and we do need a way to get to the future—they are not that future. If Henry Ford had been an educational publisher, his customers would have asked for electronic textbooks instead of faster horses.

- Apple’s announcements further iPad revolution in education, Fraser Speirs (@fraserspeirs)

How does Apple’s iBooks Textbooks initiative look from a teacher’s perspective? Kieran Healy’s post on the subject is insightful and detailed.

Apple’s proposed model would kill the used market, dead. The presentation emphasized that once you buy a book you always own it, and you can download it to any new devices you buy. But a corollary is that once you’re done with the book you can’t give or sell it to anyone else. So, at least initially, publishers can charge much less for their textbooks and make it up on volume. That’s fine by me if students end up paying less, though I immediately wonder whether the next step would be for publishers to modularize the books. Instead of your one giant Bio or Calc or Econ book for $14.99 rather than $129.99, you can have various shorter books available for the same price, but have to buy all of them over the course of a year or semester—like 19th century serial novels. This would likely be pitched to faculty as allowing for greater flexibility in curriculum construction, but again it’s the students who end up paying for the books.

- Apple for the Teacher, Kieran Healy (@kjhealy)

Apple:

We are deeply saddened to announce that Steve Jobs passed away today.
Steve’s brilliance, passion and energy were the source of countless innovations that enrich and improve all of our lives. The world is immeasurably better because of Steve.

His greatest love was for his wife, Laurene, and his family. Our hearts go out to them and to all who were touched by his extraordinary gifts.

We’ll miss you Steve. On behalf of everyone at MacStories, thank you.

Editor’s note: This is a guest post by Steve Streza, founder of Mustacheware and developer of Todolicious. Read more about him at his blog, and follow him on Twitter.

First Lodsys. Now Kootol. It seems the Pandora’s box has been opened on patent infringement lawsuits being levied against small-scale developers. What used to be a problem that only concerned large companies with massive legal teams and tons of cash to throw at patent discovery is now something that affects indies and small companies. The independent developer community has largely ignored software patents for ages, mostly because they didn’t ever get pressured by them. It was considered too small a target to go after by patent holders, considering how many bigger targets like Apple and Microsoft were often infringing the same patents. But now, with the kind of money being thrown around in the App Store (not just Apple’s, but Google’s Android Market as well), it almost seems too easy to pursue a lawsuit against a small vendor who can either kick you a few thousand bucks or spend hundreds of thousands on a patent lawsuit that will get them nothing in return.

US patent law surrounding patents has been vague and in flux for many years. In the US, Gottschalk v. Benson in 1972, it was decided that calculations (mathematical algorithms) were not patentable. In Diamond v. Diehr in 1981, a Supreme Court ruling set the precedent that computer algorithms which were parts of a larger process (in this case, making molded rubber using computer simulations) were patentable. It wasn’t until 1994 that the Federal Circuit ruled that algorithms and data structures interpreted by machines were patentable, which basically set up the current precedent that all processes interpreted by computers can be patented. This was reaffirmed in 1998 by a piece of financial software which pooled money and redistributed it; the reason this was declared patentable was because it produced something useful, and was something a human could not do manually. Compounding all of this are trade agreements between many nations (including the US) which respects patents from one country in another.

The courts have since started backtracking on this; a few rulings in the last few years may chip away at viability of some of these patents. But it doesn’t matter for already-granted patents; they can only be invalidated by time or a court, and getting it to a court is expensive and can take years. There’s an interesting thing that happens here. A patent holder risks the invalidation of their patent if they make it to trial, and the company that infringes on the patent risks having to pay damages (and possibly legal fees) if they lose. Both companies have an incentive to avoid court, so most patent lawsuits are settled out of court, preventing the viability of the patent from ever being challenged, and allowing the patent holder to continue suing other companies.

This cycle has led to the creation of the patent troll, a company with money, a legal team, a bunch of largely-obvious patents, and…well, that’s about it. These companies spend their time and resources filing for patents and pursuing companies who infringe upon them, while not doing anything of business significance with them.

Small companies have, until now, mostly ignored the threat of patent trolls, figuring that they would never go after such a small target. However, the threat has always been there. A patent is only valid if the idea has not been done before (a concept known as “prior art”), and if the patent holder actively pursues infringers. There are defenses against this (“these guys are so small, they didn’t even show up on our radar”), but generally you have to defend your patent or risk losing it. It was merely a matter of time before patent trolls began coming after the sea of cash flowing through software.

There is justified outrage at these companies for what they’re doing. Companies like Lodsys are taking advantage of patent law to harass small developers into paying up hush-money to keep from a time- and cash-consuming legal nightmares. However, it is worth noting that these patent trolls are legally operating under the rules of a broken system. It is the system surrounding patent law that must be reformed. Patent law was invented ages ago, when innovation was expensive and took a lot of time and energy. These days, any kid with a laptop can create the next huge app. The tech industry has largely figured out how to keep competitors from reverse-engineering trade secrets through a combination of mathematical and cryptographic tools. Don’t steal your way to a better product; compete your way there.

Whether Apple or Google figures out a way to shut Lodsys up is irrelevant. The patent troll hydra is out in the open; paying off one of them will cause every patent holder to consider pursuing developers with similar tenacity. With at least one indie developer withdrawing their apps from the US market so far, this spells a dark time for innovation. But only because we have been so willing to ignore the problem for so long.