July 20, 2013
Mac OS X and iOS with Objective-C and C++.
https://itunes.apple.com/jp/app/ode-inapp-oxford-dictionary/id600476372?l=en&mt=8 https://itunes.apple.com/jp/app/ldoce-inapp-longman-dictionary/id600007708?l=en&mt=8 https://itunes.apple.com/jp/app/electricviewer2/id418881872?l=en&mt=8 https://itunes.apple.com/jp/app/electricdraw-lite/id392057356?l=en&mt=8 https://itunes.apple.com/jp/app/cartoon-box/id453680717?l=en&mt=8 https://itunes.apple.com/jp/app/chan-jing-xin-wenhd/id372332300?l=en&mt=8
When Apple introduced ARC, I though it is nice but not necessary, but once I run into a project that uses hundreds of properties in classes, I realized it is hard to keep track of adding, removing and allocing, releasing those properties. But it is so easy to forget how would it work in detail when working with block by passing objects and work with core foundation objects. Although ARC is not perfect solution of all, but Now I believe ARC would save hours and hours for developer to fix memory leaks. On the other hand, Apple these days keep making changes on both OS and compiler, and that would make developers difficult to maintaining and developing multi OS version (esp. backward compatibility) proof apps.
OS X, iOS developer with DTP and design programming background. I do dictionary and newspaper apps too. I enjoy meeting people to talk about app development.