Philosophy Mondays: Human-AI Collaboration
Today's Philosophy Monday is an important interlude. I want to reveal that I have not been writing the posts in this series entirely by myself. Instead I have been working with Claude, not just for the graphic illustrations, but also for the text. My method has been to write a rough draft and then ask Claude for improvement suggestions. I will expand this collaboration to other intelligences going forward, including open source models such as Llama and DeepSeek. I will also explore other moda...
Intent-based Collaboration Environments
AI Native IDEs for Code, Engineering, Science
Web3/Crypto: Why Bother?
One thing that keeps surprising me is how quite a few people see absolutely nothing redeeming in web3 (née crypto). Maybe this is their genuine belief. Maybe it is a reaction to the extreme boosterism of some proponents who present web3 as bringing about a libertarian nirvana. From early on I have tried to provide a more rounded perspective, pointing to both the good and the bad that can come from it as in my talks at the Blockstack Summits. Today, however, I want to attempt to provide a coge...
Philosophy Mondays: Human-AI Collaboration
Today's Philosophy Monday is an important interlude. I want to reveal that I have not been writing the posts in this series entirely by myself. Instead I have been working with Claude, not just for the graphic illustrations, but also for the text. My method has been to write a rough draft and then ask Claude for improvement suggestions. I will expand this collaboration to other intelligences going forward, including open source models such as Llama and DeepSeek. I will also explore other moda...
Intent-based Collaboration Environments
AI Native IDEs for Code, Engineering, Science
Web3/Crypto: Why Bother?
One thing that keeps surprising me is how quite a few people see absolutely nothing redeeming in web3 (née crypto). Maybe this is their genuine belief. Maybe it is a reaction to the extreme boosterism of some proponents who present web3 as bringing about a libertarian nirvana. From early on I have tried to provide a more rounded perspective, pointing to both the good and the bad that can come from it as in my talks at the Blockstack Summits. Today, however, I want to attempt to provide a coge...
>400 subscribers
>400 subscribers
Share Dialog
Share Dialog
I have played around with the iPhone SDK and Apple has done an amazing job. For starters, the documentation is impressive in both quantity and quality, including a series of introductory videos (quite the contrast with the scarcity of API documentation when the Facebook API first became available). The SDK provides access to most but not all of the nifty features of the iPhone, including the camera, accelerometer and of course the gestures on the touch screen (dock access and bluetooth are not available as far as I can tell). Right now user interfaces for native apps have to be created programmatically, which is painful, but the Interface Builder will greatly simplify that (the version of the Interface Builder included in the Beta of the SDK does not support the iPhone yet). But amazingly it appears possible to create scripted applications and deliver them over the web that will be nearly indistinguishable from native apps. This is due to a number of extensions in the iPhone browser, including the ability for a web app to create a button on the phones home page, operate in full screen mode, store persistent local data in a DB and make use of advanced CSS features (still figuring out what determines if the app itself stays cached). If that turns out to work as I think it does it takes away a lot of the constraint of app delivery only via Apple (for native apps). The SDK also includes a great simulator for the iPhone, which is important given that actually deploying to the device for testing is a bit painful – I believe Apple has made this hard intentionally (requires code signing certificate from Apple and a bunch of device prep) to prevent this from becoming a back door for distributing native apps. Here is an interesting and fairly detailed scorecard for the SDK.
I have played around with the iPhone SDK and Apple has done an amazing job. For starters, the documentation is impressive in both quantity and quality, including a series of introductory videos (quite the contrast with the scarcity of API documentation when the Facebook API first became available). The SDK provides access to most but not all of the nifty features of the iPhone, including the camera, accelerometer and of course the gestures on the touch screen (dock access and bluetooth are not available as far as I can tell). Right now user interfaces for native apps have to be created programmatically, which is painful, but the Interface Builder will greatly simplify that (the version of the Interface Builder included in the Beta of the SDK does not support the iPhone yet). But amazingly it appears possible to create scripted applications and deliver them over the web that will be nearly indistinguishable from native apps. This is due to a number of extensions in the iPhone browser, including the ability for a web app to create a button on the phones home page, operate in full screen mode, store persistent local data in a DB and make use of advanced CSS features (still figuring out what determines if the app itself stays cached). If that turns out to work as I think it does it takes away a lot of the constraint of app delivery only via Apple (for native apps). The SDK also includes a great simulator for the iPhone, which is important given that actually deploying to the device for testing is a bit painful – I believe Apple has made this hard intentionally (requires code signing certificate from Apple and a bunch of device prep) to prevent this from becoming a back door for distributing native apps. Here is an interesting and fairly detailed scorecard for the SDK.
No comments yet