Copyright (c) 2011 Doron Katz. All rights reserved. DoronKatz registered under ABN 68 954 062 611. Apple, the Apple logo, iPod, iPod touch, and iTunes are trademarks of Apple Inc., registered in the U.S. and other countries. iPhone is a trademark of Apple Inc. App Store is a service mark of Apple Inc. Theme by Cory Watilo

Filed under: iPhone Development

Make sense of iOS Certificates

When developing your iOS app, you reach a point where you are ready to either build for your own device to test, or to distribute to others. The one thing that you may find that is quite fickly is certificate management. You may be using your own, or a company's or moving between one and the other for a specific project. Quite often though, you can't seem to get the certificates to work and the reasons even more confusing. Enter this open-sourced project, from @karstenBriksoft, who has provided to the community a nifty tool that allows for reasons to be given for why a certificate isn't working.

A tool that tells you why your certificates might not work. It is designed to be easily extensible and currently implements the following Certificate Problems (to add a problem, subclass CertificateProblem and implement +load,-infoObjects and -htmlDescription)

    • NoCertificateProblem: No problems found, your certificates should work
    • MissingCertificatesProblem: No Certificates were found that have a name like "3rd Party…"
    • MissingPrivateKeyProblem: No Private key found for your certificates. You need the private keys in order to sign with the certificates

As the description states, it's extensible through subclassing and implementing new problems and it's a great start for people who wish to fork and contribute to. You can find the project over at github at http://git.io/FiPXvw

Review of "Designing Mobile Interfaces"

This book centralises the science of designing interfaces, void of any specific platform or device but rather allows the reader to think spatially in terms of UX for the thumb. The Mobile developer will be able to follow the various topics or 'best practices' in a familiar theme of Problem-> Solution, with commentary and options following that. Some of the topics are quite basic, stale and non-exciting but if you can follow the book and skip over sections you don't feel is appropriate for you, then this book accumulatively is great.

I recommend this book, because it forces developers and designers to go through the basics they thought was right, re-think that and adjust, rather than cut corners and dive into the excitement of mobile development. I would take my time and read each chapter on my down time and learn something new, rather than dedicate a whole chunk of my time in one go to it. It's the type of book that is a reference than a page-to-page necessity. If you are working on an iOS, Android or Mobile Web App, this book provides themes that are device-independent in a thoughtful, comprehensive and mechanical approach. 

Bkt

Designing Mobile Interfaces

 
By Steven Hoober, Eric Berkman