iOS developers are well aware of the shift in price models away from charging up front, to free with In-App Purchase.
I have been pretty resistant to this change, especially in the light of the forthcoming ability to host preview videos on the App Store. The rationale is that getting people to buy your app without evaluating it is a massive hurdle, and a video preview could help with that.
Now I find myself having a change of heart.
Read More
A few weeks back I posted an entry called “The journey from Groovy to Objective-C”. Well at WWDC 2014 Apple announced their new language called Swift which is eerily similar to Groovy in many ways.
Today, I had to implement UITableView row re-ordering for the first time. The cells had showsReorderControl set to YES, and my delegate was implementing tableView:canMoveRowAtIndexPath: returning YES and still the handles would not show when tableView.editing was set to YES.
The solution? Your dataSource must also implement tableView:moveRowAtIndexPath:toIndexPath: for the handles to show, even if it does nothing – although it must do something to have any lasting effect on your model. The docs do state this but it is easily missed.
I was listening to Iterate 67 recently and there was discussion about Readdle‘s apps and how they work together.
I was thinking about how they achieve this above and beyond some canOpenURL: smarts, and I presume they are using a shared bundle ID or similar to allow the apps integrate with each other at a deeper level.
Somewhat tangentially this got me thinking about a possibility of solving the “there’s no upgrade pricing in the App Stores” problem.
I recently started looking for interactive books for iPad to help encourage my youngest daughter to read. Unlike our older daughter she hasn’t got a huge desire to read, but she loves the iPad and great art so I thought I’d combine the two to see if we can increase her drive to read to herself.
Read More