With the Jonnathan Dan’s article , I sense a strong case for the survival of native development.

Earlier when I on discussions with my friends who work in web development , who lead mobile projects and with people on technical forums, most of them were in one voice told that Native Mobile development will die with some shrilling Hybrid approach is best of both the worlds.

I then felt that native mobile development will in future become suitable for a niche market like Games, apps where audio , graphic rendering and where too much dependence with hardware APIs present. Other apps whose goal is to present the data alone for the users can be managed with a Hybrid app and when the app’s brand is established and when we do not have a dependency with Hardware or you get hardware access with HTML5, hybrid approach can also be killed. But reading in to his article gives me a new insight. That is,

Mobile has less space and those who use it are mostly they are busy doing something else either in travel or when they are in break, rushing in to station, chatting with their girl friend or boy friend and expects things engage quickly. They do not want to see much of their screen being occupied with loading text , spinner or which behaves clumsily not being coped to our instincts.And as for my experience I have experienced all this with Mobile Web Apps even with 3G (India) connectivity.

Any developer or a brand who wanted to keep their customer loyalty needs to offer their app with the constraint so tough to meet: Not wasting the users’ time.

HTML5 in mobile with Hybrid development or standalone app has not consistently achieved this. And Native has achieved this. But at a bigger cost and a necessity manage lot of developers and lot of code.

Big news from Texas Instruments, they’ve just released a video demonstrating the keyfob included in the CC2540DK-MINI dev kit communicating with the Iphone 4S using the GATT interface through the new Core Bluetooth API.

This is a particularly big deal because it shows the CC2540 interacting with the iPhone 4S using the stock 2540 mini dev kit without an authentication chip.

Editor’s note:Ryan Sutton-Gee is the co-founder and CEO of Y Combinator-backed PlanGrid, which offers builders the ability to store, view, and manage blueprints on an iPad. Follow him on Twitter @rsuttong.

The basic process of any construction project goes like this: A person with a lot of money (called The Owner) decides that, for whatever reason, they want a building and so they go hire an architect. This architect in turn hires a bunch of engineers and all of them start furiously designing the building until The Owner seems happy enough to move forward. Once that happens, the design is printed on piles and piles of paper and then handed to the construction team who starts the actual construction.

This is, of course, a gross oversimplification, but the interesting thing to note is that this entire exchange of information is digital — up until the point where the actual construction…

Communication to Bluetooth devices was possible with External Accessory Framework by registering in MFI program. But this case was until iOS 5 came with which came the CoreBluetooth Framework. But what is the difference between them?

External Accessory Framework:

1. To use this framework we need to be registered in MFI Program and should have made our bluetooth enabled device MFI compliant. To register here as such we need not pay for Apple. But there are costs involved in getting a certificate from third parties that your hardware does not interface with iOS device.

2. It is available for all iOS based devices that run in iOS 3.0 and above.

CoreBluetooth Framework:

1. There is no entry cost, no registration needed.

2. It is used only for devices that are compatible with Bluetooth Low Energy. (Bluetooth Low Energy is a feature of Bluetooth 4.0 which is claimed to be consuming far less power than that of classis Bluetooth devices)

3. iPhone 4S is the only supported iOS device that is BLE enabled, so Core Bluetooth Framework based app can at this point in time be supported only in that device.