Headspace pricing

Headspace advertises itself as a gym membership for your mind. I believe it is true in the sense that people attend Headspace sessions for a short period beginning of the year and then end paying for nothing.

Oh well, I do have a gym membership, so I decided to looked at the prices of Headspace as well. The yearly subscription on the web is 71,88 euros and on the iOS it’s 84,99 euros. There is a considerable 13 euros difference. Apple does take a cut on the 84,99 euros that is more than 25 euros. It would be nice to know the logic behind that price difference. Is it calculated from the real costs of doing subscription business on iOS or from a guesstimate that you can have higher prices on iOS compared to web without affecting sales?

Would you happen to have Android device to check the prices from on that platform and leave a comment below? That would be great. At the same time check out the ten free sessions, I bet they are worth your while.

headspace-pricing-web

Headspace pricing on web

 

headspace-pricing-mobile

Headspace pricing on iOS

Swift: mix and match

I’ve been putting off learning Swift for a while. While as a language it is a leap forward from Objective-C, jumping to the Swift wagon from day one wasn’t on my agenda. I wrote Bitenotes with the design from Masaichi Ikeda in Objective-C just to get it to the App Store as early as possible. Hence, I know have a small codebase which I could rewrite from scratch in Swift couple of days but as an exercise I’ll do it incrementally.

I started off with the parser and serializer. Aside from being an interesting learning experience, there was one gotcha: in the Project -> Build Settings -> Packaging, Defines Module was No and Product Module was not defined. That meant that the Xcode generated Swift to Objective-C header file wasn’t being generated.

 

Context is the key

elixia

The screenshot is from Elixia’s application while booking a class. It’s a nice app that gets the job done, but it also works as a glaring example for lacking context while doing an important action. Which class am I booking? Did I hit the right one?

In most cases the problem is more subtle. Little clues in the UI however can make a huge difference and make the user feel more at ease.

You could also question why do you need a confirmation dialog when booking a class but that’s a whole another story.

Briefs

Screenshot from giveabrief.com Screenshot from giveabrief.com

Briefs, a prototyping tool for the iOS devices, seems like a time saver. With a brief look, it however fails to deliver from a developer’s perspective – I’m not yet seeing added value compared to a working pipeline with a designer bundled with real communication. Blueprints / redlining with diffs could be a nice feature if designer and developer are not working side by side. As a mockup tool it seems great and something to keep an eye on.

Florian Kugler asks

Interface Builder – Curse or Convenience?

Storyboards are in my experience a curse. It is really annoying to get rid of storyboards halfway of the project when you realize that they are not a good fit. Single XIBs are not that bad but with some convenience methods and functions to help with the layout, pure code layout works brilliantly.