Lens•Lab for Mac OS Updated to 1.0.1

August 31, 2011

Lens•Lab for Mac OS has been updated to version 1.0.1! Here are the changes:

Bug Fixes:

  • Sensor format is now correctly set upon startup
  • Imperial measurements are now reported in feet, inches, and nearest ¼” rather than decimal

Naturally, this is a free update for all users!


iOS and Mac App Store Sales Data for Lens•Lab

August 25, 2011

I debated whether or not I should make this post. It seems like most software developers keep sales numbers close to their vests. I suppose I can see why this is (sales data being proprietary company information that might be used by competitors), but I finally decided that that rationale doesn’t really apply to me.

Let me begin by telling you who I am and why I’m here.

I’ve been a technology junky for my whole life. I’ve been using Macintosh computers since the early ’90s and had one of the original iPhones shortly after they first came out. I’ve always approached programming from the hobbyist perspective but actually got more serious about it during the job I had a couple of years ago.

I learned Visual Basic.Net to solve some pretty bad problems with a product that it was my job to support. I wrote a utility that made it MUCH easier to manage 700+ digital video recorders spread out over the state of Missouri. Being able to come up with software that makes peoples lives easier and getting paid for it was pretty cool stuff!

I’d been trying to teach myself Objective C and the Cocoa frameworks for a while. Once my son was born and I became a stay-at-home dad, I finally buckled down and began serious study.

I was also a photography nerd and I guess I got the idea for Lens•Lab when I was trying to explain how depth of field works to a friend of mine.

Basically, Lens•Lab was hatched kind of on a lark and just for fun. The $99 iOS developer fee was not too expensive so I thought, “why don’t I just put this app out there and see what happens?”

While I was developing Lens•Lab, I relied on the internet A WHOLE BUNCH. From simple problems like how a certain class works, to how apps are marketed, to how to make optimized box blur algorithms I relied on the kindness of strangers posting what they learned on the internet.

So, this is really why I’m posting this. Hopefully this data will help others out there when they are figuring out the mobile app landscape.

One more thing I should mention: I haven’t done ANY marketing or advertising whatsoever for these apps. I’ve posted to my personal Facebook (I have some 300 odd “friends”) and made a few public posts on Google+. I did get one review on 148 Apps which I will go into more. I posted in a thread on Ars Technica about the app. Other than that, these sales seem to be mostly from people finding the app on the app store or harnessing teh Googles.

So, what are the sales numbers for an cheap inexpensive, niche, hobby application released on both the iOS and Mac App Stores? Let’s get on with it!

Lens•Lab for iOS devices sales data:

  • Released 129 days ago on April 18, 2011
  • Sold 963 copies
  • This averages to 7.47/day
  • Past two weeks sales: 65
  • Past two weeks average: 4.65/day

Lens•Lab for Mac OS X sales data:

  • Released 28 days ago on July 28, 2011
  • Sold 256 copies
  • This averages to 9.14/day
  • Past two weeks sales: 101
  • Past two weeks average: 7.21/day

That’s the basic info. Let’s dig down a bit:

Here’s a chart of the iOS version of Lens•Lab since it first came out:

Here are some interesting observations:

  • There were a very large number of sales on the first few days. (Biggest sales day was release day at 98.)
  • There is a small spike around April 27 that may or may not have been because of the review on 148 Apps.
  • Sales trend more or less evens out after the first month.
  • Once sales “even out” they can still vary wildly. Some days I sell 15 copies, some days I sell 4.

Now here is the chart for the Mac OS X version:

Some interesting observations:

  • While sales are marginally strong on the first few days, there is not nearly the downward slope we see on the iOS version.
  • We still have a pretty wide variation in sales from day to day.
  • We’ll know more about how the Mac OS version is doing as time goes on.

Some other things to note:

  • Pretty close to 50% of all sales are from the US. Of the rest of the world, the markets break down like so:
    • US: 50%
    • UK: 10%
    • Germany: 7%
    • Canada: 7%
    • Australia: 6%
    • Italy: 5%
    • France: 4%
    • Etc…

So one big question is: what explains the massive boost in sales in the first few days of the iOS version? I think the answer might be two-fold: better discoverability for iOS apps, and being in the “what’s hot” section of the iOS App Store. For iOS users, there are more avenues to discovering new apps (both via the device itself and the iOS App Store in iTunes) than there is for Mac OS X apps. Also, Lens•Lab was in the “new and noteworthy” section of the iOS App Store for a couple of weeks pretty soon after it was launched.

Another question is this: why are there almost twice as many sales for the Mac OS X version than the iPhone version, especially considering the Mac App Store has to be at least an order of magnitude smaller? This may be a bad question as the Mac OS X sales may dwindle just like the iOS numbers did. I’m kind of going on “data after one month”. But I think what’s going on is this: there is an expectation that iOS apps should be cheap or free. Basically, even though I’m not really competing with other fancy depth of field calculators, I’m still competing with all the other apps that sell for 99¢ that do far more. So, a small/one-trick pony type iOS app is not that great of a deal for 99¢. Compare this with the Mac OS X app store where you routinely see apps for $30 or $60 or $300. Compared with those, a little 99¢ app is a deal.

Now, let’s play some “what-if?” games.

Suppose I had 10 different little utility apps on the iOS and Mac App Stores. Suppose I charge 99¢ for them. How many would I have to sell a day to make a “decent” living?

10 apps, selling at 99¢ apiece, each selling 20 copies a day (not unreasonable), would net you $51k a year. Not a bad living for a self-employed app developer. I’m not saying that I make this (I only have one app out) I’m just trying to see what is realistically possible.

Anyway, I hope these can help some smaller developers out. Keep in mind that this is not my “job” (full-time father is), it’s really a hobby that’s paying for itself plus a bit more. I had no idea how much money I might make with this (I really just hoped I would make back the developer costs) but I’m totally delighted and happy with the sales numbers I have. Do you have any thoughts on these numbers? Does this help you as an app developer? Leave a note in the comments!

Last but not least, thanks to all of you who purchased Lens•Lab!

11″ MacBook Air, Core i7: FAST.

August 12, 2011

So my beautiful and talented wife got an 11″, Core i7 variant of the mid-2011 MacBook Air to write her dissertation on. (The purchase timing was pretty good as her white MacBook’s hard drive just died.) I played around with the Air for a bit and holy moly, it’s FAST!

To compare, the computer I do almost everything on (including software development) is a mid-2009 13″ MacBook Pro. It’s got 4GB of RAM, a 2.26Ghz Core 2 Duo processor, and a 80GB Intel X-25M (G2) solid-state hard drive. I love this laptop and it’s still in great shape more than two years into owning it.

The Air has 4GB RAM, 128GB Samsung SSD, and the upgrade 1.8Ghz Core i7 processor. I’m really impressed with Core i7 processor. This one has two cores but can handle two threads per core for a total of 4 threads. I’d heard about HyperThreading and have used computers whose processors had this feature, but I wanted to sit down and investigate this from a programming perspective. HyperThreading has its limitations but depending on the workload it can provide some pretty stunning benefits computationally.

I’ve blogged about NSOperation before, so you know I’m a fan of this class. While the child was taking his morning nap, i whipped up a little app that spawned 4 NSOperation objects either parallel or in series. The actual work that the NSOperation is doing is totally simple and shouldn’t be considered authoritative or particularly indicative. (I just adds the square root of [NSDate date] to a variable 20,000,000 times. I figured: we have some addition, some floating point math, and an Objective C call. That’s close enough for a ball park idea of what this thing can do.

When I run this on my 2.26Ghz Core 2 Duo MacBook Pro, I get this:

  • Time to run all threads in parallel: 3.58 seconds
  • Time to run a single thread: 1.78 seconds
  • Total work (1.78 * 4 = 7.12) gets done in 3.58 seconds. This is a 2.0x multi-threading improvement.

When I run it on the 1.8Ghz Core i7 I get this:

  • Time to run all threads in parallel: 1.74 seconds
  • Time to run a single thread: 1.22 seconds
  • Total work (1.22 * 4 = 4.88) gets done in 1.74 seconds. This is a 2.8x multi-threading improvement. (It’s almost like HyperThreading adds a third core to the processor.)

What do we learn from this little experiment? The Core i7 is a really fast processor. For my little contrived test we see that not only is the i7 45% faster than a 2.26Ghz Core 2 Duo for single threaded applications, it’s over twice as fast for multi-threaded applications!

One thing you should know about the Core i7: it doesn’t actually run at 1.8Ghz. AnandTech has a really cool chart to illustrate this but basically, the processor has a maximum TDP (thermal design power) and the processor can dynamically over clock itself depending on temperature and load. This is a really cool (har har) idea and it’s interesting and refreshing to see CPUs marketed with a lower clock speed than they are actually capable of.

If you want to download the Xcode project for the super hacked together and not very pretty Threads application, you should very gently click here and don’t make fun of me when you look at it.

Lens•Lab for iOS development update.

August 4, 2011

Greetings, fellow photography nerds!

We’re working on an update to Lens•Lab for iOS devices. Here’s what we have in store:

  • Editable constraints for focal length. For example, I can set the focal length to go from 24mm-85mm, just like the lens I currently have on my Canon 10D.
  • Editable constraints for aperture. For example, I can set the aperture to go from ƒ/3.5 to ƒ/22, just like the lens I have on my Canon 10D.
  • Aperture values are straight decimal values now. (They used to snap to 1/2 stop increments but now it’s more versatile.)
  • A new Lens Information panel with the following information:
    • Sensor Size & crop factor information.
    • Angle of View (Vertical, Horizontal, Diagonal).
    • Plane of Focus (Vertical, Horizontal, and Diagonal size of the focal plane.).
    • …also for Depth of Field Near and Depth of Field Far.
  • …and more!

We are excited about this release! If you are interested in trying this version out before it goes public, leave a message here or send an email to jmenter+blog [at] gmail [dot] com.