Editing Mobile device code
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
'''Mobile device code''' is presently complex and difficult to write. | '''Mobile device code''' is presently complex and difficult to write. The emergence of [[Python]] on some [[Nokia]] platforms is very encouraging, and according to its own R&D division, 1000 lines of [[C++]] can be replaced by 11 lines of Python in a typical application. They also demonstrate [[RFID]] as a feature of their new phones, making [[Consumerium Services]] incredibly easy to implement for those products that have an [[RFID tag]]. | ||
Also a likely future trend is the embedding of [[Near Field Communication]] technology, which allows instant communication for devices within 15cm distance of each other, to mobile phones, which would be even more handy for Consumerium since the [[product identification]] could be done via embedding NFC devices into the store shelves. | |||
Also a likely future trend is the embedding of [[Near Field Communication]] technology, which allows instant communication for devices within 15cm distance of each other, to mobile phones, which would be even more handy for Consumerium since the [[product identification]] could be done via embedding | |||
Issues with mobile device code: | Issues with mobile device code: | ||
*reliability (phones aren't allowed to "crash") | *reliability (phones aren't allowed to "crash") | ||
*[[location-based services]], e.g. relying on [[OpenGIS]] | *[[location-based services]], e.g. relying on [[OpenGIS]] |