A link on Twitter today to an app called FiftyThree lead me to their demo video.
Does anyone use the iPad on the go like this? Is the iPad truly passing onto the realm of Moleskine notebooks where you carry the thing around in your hand (it’s just too heavy for me)? If I was creating a commercial for Samsung’s new Galaxy Note – which actually comes with its own über stylus – I’d look at this.
Otherwise, very neat app indeed…
Say what you will, this is pretty cool – at least at the idea level: a specialized, HTML5 web browser for mobile devices that provides special hooks for HTML5 apps granting them access to native device features. Pretty nifty, right? Naturally the people who control the platform, kinda get to decide what can and cannot run, maybe get a cut of the action for the business that they are generating for you and for the work that they invested in making and marketing the app.
In exchange for openness, you get cool features (especially for games) and capabilities you otherwise will not be able to provide. Tradeoffs tradeoffs. Still, pretty darn cool.
An app we were building for the iPad was recently approved by the client. Being a more capable organization, the client wanted us to build the app for them using their Apple developer and app store credentials for submission. To do that they sent us the three necessary files:
I also modified the app's bundle identifier to reflect the identifier specified by the client.
I merrily added the keys and certificate to the OS X key chain. Yet Xcode was unable to build using these updated credentials. The error that was reported was:
"Profile does not match any valid certificate/private key pair in the default keychain"
After digging around I pinged my friend Glenn Martin from Intrepid Development to see if he knew what was wrong. Glenn actually knew what went wrong: apparently OS X 10.6.8 imports keys to the System key chain instead of the Login key chain. Xcode only looks at the Login key chain. All the was necessary to fix the issue was to drag and drop the key in the Keychain Access application from the System key chain to the Login one. Mindless fix to a truly frustrating problem.
Hope it helps you.
