Development kits in the field of electronics can cover many different types of systems from the simple demonstration of a devices capabilities using switches and LED's to complex multiple microprocessor setups with lcd screens, sensors and other man machine interfaces. One thing they all usually have in common is that once one has worked on a system and become familiar with a device then the kit is packed away and gathers dust in some corner and the designer must then take the next step of designing the device into his end product. I have worked with a number of different kits over the years, the latest being the Atmel SDK500, Wavecom Q24 and the MaxStream wireless development kit for the XBee range of Zigbee modules.
The ideal kit for me is one in which one can learn about the device or module in question and then use it in a practical fashion. I am currently working on a system which combines a PIC 16F876 and an XBee module. When the system is complete, a user will be able to not only learn about the workings of the XBee wireless module using a PC as an interface but by writing some software for the 16F876 the user will have a complete Zigbee system capable of operating as a standalone Coordinator or End unit. The system will allow End units with the same PAN ID's to join and the data gathered by the End unit will be available to the PC via the Coordinator.
This type of setup allows two types of configurations to be set up. The user can select to communicate directly with the Zigbee Coordinator module and therefore to have access to all its capabilities via its AT command set. The user will then not only have access to the local device but also all the data being received from the End units (assuming they have been set up to gather and transmit their data either by time or input change). End units can also be accessed by either using the broadcast or unicast mode capabilities of the XBee modules.
The user can also elect to leave the wireless communications to the PIC microcontroller and just access that information when needed. This will allow the Coordinator to gather data as the End units transmit it, store it in an internal EEPROM memory and pass it on to a PC when requested to do so.
This type of arrangement constitutes a better development kit for me than the custom standalone units supplied by most manufacturers. One that is indistinguishable from a final product and one that is familiar as we have not only learned to develop on it but it is also a practical working product usable in the field.