Mobile device code - Revision history

Jukeboksi: note about Symbian and Java

2004-02-22T17:53:11Z

note about Symbian and Java

← Older revision		Revision as of 17:53, 22 February 2004
Line 1:		Line 1:
	'''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]].		'''Mobile device code''' is presently complex and difficult to write.

			Currently the most widely adopted "smart" mobile device platform is [[Symbian]] expecially the [[series 60]] flavor developed and licenced by [[Nokia]]. Series 60 Symbian supports native C++ programs, [[Java]] [[MIDP]] and apparently [[Python]] is being introduced now.

			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 [[NFC]] devices into the store shelves.

142.177.108.61 at 16:09, 22 February 2004

2004-02-22T16:09:13Z

← Older revision		Revision as of 16:09, 22 February 2004
Line 1:		Line 1:
	'''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]].		'''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 [[NFC]] devices into the store shelves.

	Issues with mobile device code:		Issues with mobile device code:

			*direct support for [[NFC]], [[RFID]] and [[barcode scanner]] - probably all three methods will be required and can back each other up redundantly
	*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]]

Jukeboksi: note about Near Field Communications as a possible trend in the future

2004-02-22T15:42:44Z

note about Near Field Communications as a possible trend in the future

← Older revision		Revision as of 15:42, 22 February 2004
Line 1:		Line 1:
	'''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]].		'''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.

	Issues with mobile device code:		Issues with mobile device code:

142.177.108.61 at 15:23, 22 February 2004

2004-02-22T15:23:33Z

New page

'''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]].

Issues with mobile device code:

*reliability (phones aren't allowed to "crash")
*[[location-based services]], e.g. relying on [[OpenGIS]]
*simplicity of user interface and language used in it
*standardization across [[mobile device vendor]]s
*integration with [[wiki code]]