Here is my summary of the past month in links.
As the days went by, what seemed like a huge scandal at first turned out to have been blown out of proportion. Still, some phone carriers are to be blamed for using Carrier IQ’s software to track things like the applications used or what URLs are visited by a user (information which, admittely, they know anyway).
Android Graphics Architecture vs. iOS
There has been an interesting discussion about the shortcomings (or not) of Android’s graphics architecture vs. iOS. It’s hard to follow the original discussion now because many of the posts have been edited but let’s recap:
Dianne Hackborn, Android engineer at Google, set out to correct some assumptions about Android’s internals in a post titles How about some Android graphics true facts?. Andrew Munn, former intern on the Android team, followed up with his (misinformed) post The Reason Android is Laggy, claiming the main advantage of iOS’s over Android’s architecture was that iOS used
a dedicated UI thread with real-time priority.
In another follow-up post, Dianne Hackborn rejected this claim, instead naming the security model and the design of certain APIs as reasons for Android’s past performance problems. Several people also pointed out flaws in Andrew’s description of how iOS actually works (see Andrew Munn’s updated post). Bob Lee’s post The truth about Android & iOS UI performance on the topic is worth reading, too.
In conclusion, it’s probably fair to say that with Android 4.0, the technical differences between iOS and Android in terms of graphics rendering are pretty small. I really like Brent Royal-Gordon’s take on the topic, quoted by Andrew Munn:
All that stuff you noticed—the way images aren’t drawn into lists while you’re scrolling, the way WebKit rendering stops when the system is tracking a touch—isn’t inherently built-in by a mechanism that pauses the world when a finger is on the screen.* It’s deliberate behavior painstakingly implemented by the developer of each individual app.
This is not a technical difference; it’s a cultural difference. Good iOS developers don’t ship software until it runs at something near 60 fps while scrolling and tracks touches almost perfectly; good Android developers do.
Gwynne Raskind gives a good introduction to reading ARM assembly language. This can be useful for intense iOS debugging sessions or if you just want to better understand your compiler. Don’t miss part 1 and part 2 of the series covering x86_64 assembly.
Zhu Levey created an open-source implementation of the animated fly-out menu made popular this month by the redesigned Path app. While I hope we won’t see this kind of menu in every second app in the future, the code can help illustrate some advanced Core Animation techniques.
Another UI gem in the new Path app is the floating clock that scrolls and animates with the main scroll view to indicate the position of the timeline. Florian Mielke shows how to mimic this behavior in your own view controller.
Update Janurary 1, 2012: TimeScroller by Andrew Roy Carter is another take on this. Andrew’s solution goes a little further and actually reproduces the look of the control in the Path app including the clock.
Guy English on the possibility of Apple providing developer access to Siri in the future.
I predict that a Siri API is further off than you might think. The integration of services into Siri appears to be on a very case by case basis and even an internal app required special consideration. … Apple doesn’t appear to have an internal API for Siri yet, and it’s my bet that they’re a year or so away from it.
Someone naming herself Subjective Observer points out a very useful new Core Data option in iOS 5 and OS X Lion. The Core Data editor now lets you “use scalar properties for primitive data types” instead of
NSNumber, generating accessors based on scalar data types for numeric attributes. That is a great and largely undocumented addition! She also shows how to make use of this new feature while maintaining compatibility with older OS versions.
It’s common Cocoa wisdom and the rule to put each window into its own NIB file. Joshua Nozzi argues that it’s not always beneficial, though.
Blind adherence to generalizations will get you in trouble.
VendorForge and Vendor, two of the Cocoa package managers I mentioned in last month’s link roundup, have merged to form VendorKit. I hope to see more of this. One package manager to rule them all! (Provided it’s a good one.)
Stuart Carnie clears up a syntax rule in C that always eluded me before: where to put the
const keyword in a complex declaration? The answer is, of course, it depends on whether you want a constant pointer to a mutable value or a mutable pointer to a constant value or a constant pointer to a constant value. For all these cases, Stuart comes up with an easy-to-remember rule:
constto the right and read the declaration from right to left.
Simple as that.
“Junior B.” compared the performance of various open-source JSON libraries to Apple’s new built-in JSON parser in Cocoa. Result: on iOS, JSONKit is up to ~30% faster than Apple’s
NSJSONSerialization. SBJSON and TouchJSON are much slower than both.
CMPopTipView by Chris Miles is a view component that can display a UIPopover-like “bubble”, containing a text message, pointing at a specified button or view. Looks good for help texts.
Mark Edwards analyzes the benefits of trying to optimize PNG images for your apps.
I’m going to come straight out and say it—if you’re spending any effort compressing or optimising your PNG images for iOS app development, you’re wasting your time.
Great post by Jonathan Wight on the current shortcomings of Storyboarding in iOS 5 apps. Jonathan’s verdict is that, while Storyboarding is a promising concept, it isn’t yet mature enough to be used in a complex app. I was particularly struck by the section titled “Misuse sender field”. It really seems Apple has forgotten to provide an essential API here.
If you ever find yourself logging retain counts while trying to debug a memory management problem, remember Bill Bumgarner’s post and stop what you’re doing immediately.
Noel Llopis investigates the benefits and performance drawbacks of using OpenGL multisampling in iOS. In his testing with the Flower Garden app, the performance impact varied greatly by device: almost none on the iPhone 3GS and iPad 2, huge impact on the iPad 1 and iPhone 4 (whose GPU is less capable relative to the amount of pixels they have to handle).
Jim Dovey wrote a simple socket class that illustrates how to work with Grand Central Dispatch’s dispatch sources and dispatch I/O channels. Both are GCD features that are usually not addressed in your typical GCD tutorial so Jim’s code should be very useful if you want to learn more about the topic.
F3BarGauge by Brad Benson is a customizable iOS control to display bar gauges. Useful for your next audio mixer/visualizer app.
Justin DeWind wrote an up-to-date tutorial on building frameworks in Xcode that include multiple architectures such as armv6, armv7, and i386. This is especially useful for developers of open-source components. Or you can build your own frameworks if you want to easily mix ARC and non-ARC code without the hassle of specifying per-file compiler flags.
John Carmack talks about the huge benefits he got from using static code analysis in his projects. The discussion of particular tools is C/C++-centric and thus not directly applicable to Objective-C code but his general findings are interesting:
The most important thing I have done as a programmer in recent years is to aggressively pursue static code analysis. Even more valuable than the hundreds of serious bugs I have prevented with it is the change in mindset about the way I view software reliability and code quality. … I feel the success that we have had with code analysis has been clear enough that I will say plainly it is irresponsible to not use it.
Lesson for Cocoa developers: at least use the Clang Static Analyzer that’s built into Xcode regularly.
Grant Paul reverse-engineered how Siri authentication works, thereby ensuring that it only runs on an iPhone 4S (or for hacks you need an iPhone 4S device token). This is his overview.
Noel Llopis gives a good tutorial (including a demo project) how to sync files with iCloud in the simplest way possible (without using
Nice little tip by Shane Crawford. Especially useful if you use some open source library whose author did not care to fix all compiler warnings.
Great post by Jessica Hische on the fine line between being inspired by others and using this inspiration to create something original and blatantly copying others’ creations.
Michael Shephard from Black Pixel about the iterative and non-linear nature of the design process. Nice insight.
Justin Williams shows what happens when media companies create apps for the sake of having an app rather than to create a better user experience.
I’m convinced that the people who actually write for magazines, edit them and publish them have never actually tried using their iPad versions for more than a few moments. If they actually did try to use their publication’s app as the actual means to read each issue, things would have to improve. Right? RIGHT?!
UI Parade is another one of the sites that collect examples of outstanding UI design. I mentioned a number of these over the past months in my blog posts but this one seems particularly well edited.
David McKinney illustrates different approaches how to integrate help into your app’s UI. I like the integrated approach they settled on very much.
The Flipboard for iPhone design process
After Flipboard for the iPhone came out earlier this month, members of the design team tweeted some pictures showing the many, many iterations they did for this one app’s design. I love how the photos illustrate the incredible amount of work that went into it.
Brenden Mulligan took a very detailed look at the new Path app from a design and user experience point of view. Very insightful and spot-on.
Justin Williams on the importance of texture in the iOS UI. Justin gives examples of some new apps that to him feel out of place on iOS because their design is based on solid colors without texture, which seems more fitting in Android and Windows Phone environments. He points out the importance of designing especially for the target platform:
Mobile is young enough that we’ve got three vibrant platforms that offer uniquely identifiable experiences jockeying for position. If your goal is to reach all of those customers, do it with respect and taste. Build something tailored specifically for them, not something that is just “good enough” for all three.
Fraser Speirs posted a video that shows how competently his 4-year-old daughter uses the Brushes app on the iPad to paint a picture. Again and again, it’s amazing to see how much more intuitive these post-PC devices are compared to a classical mouse-driven GUI.
Oliver Reichenstein continued to analyze and publish iA’s pricing experiments with their app, iA Writer. The takeaway from this for developers seems to be: trying out different price points is fine and all but in the end, the quality and uniqueness of your app will be a much bigger sales driver:
To increase sales: Don’t imitate. You might get some crumbs from some table but ultimately, you’ll help the original by doing so. Innovate. Think different, be different. Take maximum care for details, even if it’s a hassle. Read all feedback and don’t get irritated by feature requests and focus on the next big step.
Taking the new Path app as an example, Dan Frommer points out how hard it is to be successful on the App Store these days, even if you made a great product and got as much press as those guys did. A few days later, Dan followed up with a post showing that in Path’s case at least, the app finally made it into the top 25. So it may be hard, but it’s definitely not impossible.
In a press release, Apple announced some numbers for the Mac App Store now that it is almost one year old. 100 million app downloads in less than a year sure sound impressive until you compare it to the size of the iOS App Store, which registers about 1 billion downloads a month.
In other words, the iOS App Store is about 50-100 times bigger than the Mac App Store in terms of downloads. Interestingly, the relation is about the same when you count the total number of available apps (500,000 for iOS vs. less than 10,000 on the Mac App Store). So arguably, because it’s so much easier to get your share of visibility on the Mac App Store, your chances of making money could be roughly equal on both stores, especially since Mac apps tend to be priced higher.
Dan Frommer also takes a look at the numbers in the Mac App Store. According to his statistics, only
about 18 apps are added to the Mac App Store each day. Surprising.
According to Flurry (who have unique data on many mobile app stats thanks to their analytics software), app developers still favor iOS over Android by a wide margin despite Android’s tremendous growth in market share. The main reason seems to be that the App Store is where the money is.
Research firm Distimo published an updated report on the mobile app store field in 2011. Key findings:
- The iOS App Store generates about four times the revenue that the Android Market makes.
- In-app purchases and freemium business models have an increasing share of the total revenue.
- The app market in China is growing fast.
Good interview by Kathleen De Vere with David and Ian Marsh, the twin brothers behind Tiny Tower. They talk about monetization strategies on the App Store and the increasing role of “freemium” business models. Surprisingly to me, 30% of the revenue they make with Tiny Tower comes from selling $30 in-app purchases, even though these items only make up 4% of all their in-app purchases. Goes to show that it pays off to give your most loyal users the chance to give you more than $0.99.
Matt Gemmell makes the tongue-in-cheek argument that it is okay to only support the latest OS version. And I actually agree (up to a point).
David Haywood Smith from The Kernel says there has never been a better time to be a developer. There are countless resources and opportunities available to us. The only thiing we have to do is consume them. But at the same time, David reminds us that we all have the responsibility to give something back to this awesome community. Everybody should think about how they can contribute. And to all those who already do contribute, do not sit back:
The big challenge is leading. It’s not as scary as it sounds. It’s really just an extension of contributing. If you make a significant contribution then you automatically become a leader. … I encourage you to start thinking about how to move up the ladder. Whatever kind of developer you are, you’ll find it pays dividends.
On the same topic, Matt Gemmell has some very useful tips on how to publish some of your code in open-source form. By following Matt’s advice, you increase the chances that your open-source project will actually be noticed significantly. Even if your code is absolutely amazing, almost no one will look at it if you don’t package it nicely and make it easy for others to use.
Nicola Armellini from Jumpzero talks about the development process of their Mac app, Gradient. I love how he stresses to start out with a simple idea that solves a real problem and the importance of prototyping and showing what you do to possible influencers far before it’s done.
Google reported on their blog that the Android Market has reached 10 billion app downloads. The current growth rate of the Market is 1 billion downloads per month, similar to the current growth of the iOS App Store.
The guys from Shifty Jelly make quite a convincing point for iOS developers to also look at the opportunities of the Android community.
In many ways it’s [the Android Market] a better place to be than iOS, since so many developers are ignoring it, and yet there is a massive install base waiting to give you their money.
I’m sure there are many Android developers who would agree. So why all the controversy? Let everyone decide on their own which platform they want to target (first). I am sure some will follow Eric Schmidt’s prediction and others (probably most, at least in the next 6 months) will not.
Mary Jo Foley writes that Microsoft may make a 180 degree turn and actually make Windows 8 tablets Metro only, not bringing over the traditional Windows desktop. I think that would be a great move for Microsoft.
Antoine Leblond from Microsoft gives developers a preview of the upcoming app store for Windows 8. Their feature set sounds great:
We have full platform support for free apps, trials (both time-based and feature-based trials) and paid apps, including in-app purchase. And we have sales analytics that will help you target customers more effectively.
In addition, developers will get an 80% revenue share (instead of the usual 70%) if their app is successful enough to make it over $25,000 in total revenue. Let’s hope that more competition in the app store space will give Apple the incentive to further improve their offerings.
Press release by HP. Will it make a difference? Will other major players like Facebook or Amazon now adopt webOS for their own devices? In an interview with Joshua Topolsky for The Verge, HP CEO Meg Whitman and board member Marc Andreessen at least confirmed that HP has plans to make new tablets running webOS,
but what I can’t tell you is whether that will be in 2012 or not.
Alasdair Monk’s is one of a number of very positive reviews of the Lumia 800, Nokia first device running Windows Phone 7.5. The phone is stunning and the software looks great too. Looking at the market reaction, it still seems to have come too late.
Matthew Baxter-Reynolds just published a rather negative review of his Lumia 800 experience over the last month, citing many minor flaws both in the built-in software and in third-party apps.
What’s wrong is the niggles. Windows Phone is a good operating system. But it’s not a great operating system. … It’s the niggles that’s stopped me from developing a deeper relationship with the device that turns it into a ubiquitous tool, as opposed to “just a phone”.
Apple and Steve Jobs
MG Siegler summarizes Apple’s 2011 for Techcrunch in a long list of links. Very useful post for reference if you want to find a particular article again.
Dan Frommer highlights some key points how Apple works and acts. Realizing these traits will probably make it much easier to tell if the next random Apple rumor has any value or not. Most important lesson for developers:
The iPad really is special. If you did not know that already.
Apple has been extremely busy recently suing its competitors (and being sued by them) for patent infringement, copycat design, etc. I think it’s fair to say that it has become impossible to say who’s right and who’s wrong overall. Not so in this particular case: Jason Kincaid seems to have uncovered that Apple may have cooperated with a patent troll. To quote Jason, it’s
hard to see Apple in a positive light here.
Thomas Q. Brady with a well-written and well-founded critique of the Jobs biography. Brady makes many of the same points I already heard from John Siracusa, so this is a good article to read if you don’t listen to podcasts.
Gary Ng’s article includes links to many new renderings and plans of Apple’s stunning plans for the new corporate campus.
In the Steve Jobs biography, Walter Isaacson suggests that Steve Jobs himself wrote much of the “Here’s to the Crazy Ones” text for Apple’s famous Think Different campaign. In this interesting article for Forbes, Rob Siltanen, member of the original advertising team, tells a different story. Obviously, this is not development-related at all, but it is a good read.