The good people at Itty Bitty Apps interviewed me about Soundproof and how we use the excellent Reveal app to debug and design these elements. [You can find the interview here](http://revealapp.com/blog/revealed-soundproof.html)
When we first released Soundproof we had to make the difficult decision to delay polishing our VoiceOver experience for accessibility users. We had done some work on this already, but due to the nature of our custom UI elements such as the time scrubber and Count-In screen, the work was too much to complete first time around. In hindsight, I really would like to have done this for the first release. It seems to be […]
I recently wanted to start covering start writing all my new app code in Swift, but hit a big problem: I use CocoaLumberjack everywhere and its not ready for Swift yet. They are working on this right now for a 2.0 release. I checked around github and it seems some good work is being done on this. However the missing piece was very important: because Swift lacks conditional defines and a macro preprocessor, all arguments […]
During the process of making Soundproof, we had to consider what the business model would be. I wrote [some early thoughts about pricing](http://transition.io/is-unlock-everything-a-mistake/) and talked about some [issues with implementing upgrade pricing with In-App Purchases](http://transition.io/my-first-public-ios-app-is-now-available/) previously. Here, we’ll take a brief look at the experience of implementing In-App Purchases and the user experience.
In this second article in the series about the making of our [Soundproof music practice App](https://itunes.apple.com/app/id889019884), I will explain some of the details and decisions behind the Repeat Markers feature.