Firstly, thanks to those of you who have taken the time to explore LockInfo 5 and helped other people out with questions and concerns. It’s always nice to have people “in the trenches” helping out while my inbox is getting filled with emails.
To those of you that have voiced concerns about the direction LockInfo 5 has gone, it’s worth reading my blog http://blog.dba-technologies.com/pos…kinfo-rebooted to understand the design thoughts I had when approaching this project. The decisions were not made haphazardly.
My rationale for the rewrite, for those of you who are not technical, is that the original LockInfo code base, the one that powered LockInfo 4, is three years old and is based heavily on code that existed back in iOS3. It didn’t leverage new frameworks like Theos or new iOS frameworks. It didn’t integrate will with the notification system and resulted in a lot of inconsistency with the state of the system. The iOS ecosystem is very different now and the maintenance costs of LockInfo had reached the point that a rewrite was necessary. And when it came time to rewrite, I also looked to simplify the overly complex settings that LockInfo 4 and earlier came with.
I do want to have satisfied users. I do want to continue to iterate on LockInfo 5 to provide a tool that everyone will enjoy using. That will not be LockInfo 4 on iOS6 - that’s just not going to happen. But it will be a new LockInfo that supports some of the features of LockInfo 4, but many that LockInfo never had. It will support a standard plugin architecture that will allow it to use any NC widget.
If there are usability issues that you feel need to be addressed, email me. I may not be able to reply immediately (I’m focused right now on license issues and critical bugs) and you may not see those features immediately in the product, but I do want to continue to improve LockInfo.
Email me at support (at) dba-technologies (dot) com.
All I ask is for the conversation to be constructive.