The problem with using the proprietary gadgets of a particular device is that as you move your application to another platform or device, those gadgets would look out of place. Similarly, if we provided a lot of high level gadgets, everyone's apps would look like AppGameKit apps (anyone remember SEUCK)
Fortunately AppGameKit is equipped with some of the smartest sprites around, capable of detecting when they are pressed and responding with a wide range of visual toys. You can imagine the AppGameKit sprite as a simple button gadget, which can be positioned, sized, transformed when selected and hidden at will. Almost every gadget you can think of can be whipped up in a few minutes using sprites alone. The ability to overlay text makes them even more useful.
I am sure it won't be too long before an AppGameKit user writes an #include file which creates all the gadgets you need, entirely made from sprites!
The great thing about doing it this way is that your engineering application looks consistent across all the devices you deploy it to, meaning your end users only have to learn it once and instantly recognise it, no matter what device it is running on. It also benefits from looking unique to you, allowing your own design ideas and styles to come through.
I remember creating a small prototype of a business app on the iPhone using their gadgets. When I had finished, it looked like every other business app I had ever seen on the iPhone. It did the job, but it wasn't that inspiring
