IFD:IOSDev/Projects/Michaela - Revision history

Michaa: /* Technical Realization */

2011-08-07T18:50:08Z

Technical Realization

← Older revision		Revision as of 18:50, 7 August 2011
Line 84:		Line 84:
	Furthermore, this mobile API enables an external management service to finally configure the mobile content. Such an external service is mostly a company that is primarily specializing in concerns of the mobile web. They direct a heavy expertise of mobile software & hardware as well as mobile usability. Currently a quick & high divided developement underlies the age of the mobile technology. The cooperation with such external services ensures that the e-shop always offers up-to-date mobile content.		Furthermore, this mobile API enables an external management service to finally configure the mobile content. Such an external service is mostly a company that is primarily specializing in concerns of the mobile web. They direct a heavy expertise of mobile software & hardware as well as mobile usability. Currently a quick & high divided developement underlies the age of the mobile technology. The cooperation with such external services ensures that the e-shop always offers up-to-date mobile content.

	Finally the request of a mobile device to the URL of an e-shop enables the application framework to chek out ~~the~~ relevant ~~technical~~ information. As you can see in the figure, the redirection to the mobile page passes the management service & the mobile content can be processed back to the requesting device.		Finally the request of a mobile device to the URL of an e-shop enables the application framework to chek out its technical relevant information. As you can see in the figure, the redirection to the mobile page passes the management service & the mobile content can be processed back to the requesting device.

Michaa: /* Technical Realization */

2011-08-07T18:48:33Z

Technical Realization

← Older revision		Revision as of 18:48, 7 August 2011
Line 76:		Line 76:

	==Technical Realization==		==Technical Realization==

			[[Image:Process-of-a-mobile-request.jpg\|right\|thumb\|300px\|The Process of a Mobile Request]]


	The setup of the visual interface has to be implemented via the application framework of the specific e-shop software. Therefore the application framework provides a so called mobile application programming interface (short: mobile API). This mobile API threads the necessary content information for every single request of a mobile device. A markup language (e.g. HTML5) predefines the layout of the requested mobile page.		The setup of the visual interface has to be implemented via the application framework of the specific e-shop software. Therefore the application framework provides a so called mobile application programming interface (short: mobile API). This mobile API threads the necessary content information for every single request of a mobile device. A markup language (e.g. HTML5) predefines the layout of the requested mobile page.
Line 82:		Line 85:

	Finally the request of a mobile device to the URL of an e-shop enables the application framework to chek out the relevant technical information. As you can see in the figure, the redirection to the mobile page passes the management service & the mobile content can be processed back to the requesting device.		Finally the request of a mobile device to the URL of an e-shop enables the application framework to chek out the relevant technical information. As you can see in the figure, the redirection to the mobile page passes the management service & the mobile content can be processed back to the requesting device.
	~~[[Image:Process-of-a-mobile-request.jpg\|right\|thumb\|300px\|The Process of a Mobile Request]]~~

Michaa: /* Technical Realization */

2011-08-07T18:48:09Z

Technical Realization

← Older revision		Revision as of 18:48, 7 August 2011
Line 82:		Line 82:

	Finally the request of a mobile device to the URL of an e-shop enables the application framework to chek out the relevant technical information. As you can see in the figure, the redirection to the mobile page passes the management service & the mobile content can be processed back to the requesting device.		Finally the request of a mobile device to the URL of an e-shop enables the application framework to chek out the relevant technical information. As you can see in the figure, the redirection to the mobile page passes the management service & the mobile content can be processed back to the requesting device.

	[[Image:Process-of-a-mobile-request.jpg\|right\|thumb\|300px\|The Process of a Mobile Request]]		[[Image:Process-of-a-mobile-request.jpg\|right\|thumb\|300px\|The Process of a Mobile Request]]

Michaa: /* Technical Realization */

2011-08-07T18:47:51Z

Technical Realization

← Older revision		Revision as of 18:47, 7 August 2011
Line 79:		Line 79:
	The setup of the visual interface has to be implemented via the application framework of the specific e-shop software. Therefore the application framework provides a so called mobile application programming interface (short: mobile API). This mobile API threads the necessary content information for every single request of a mobile device. A markup language (e.g. HTML5) predefines the layout of the requested mobile page.		The setup of the visual interface has to be implemented via the application framework of the specific e-shop software. Therefore the application framework provides a so called mobile application programming interface (short: mobile API). This mobile API threads the necessary content information for every single request of a mobile device. A markup language (e.g. HTML5) predefines the layout of the requested mobile page.

	Furthermore, this mobile API enables an external management service to finally configure the mobile content. Such an external service is mostly a company that is primarily specializing in concerns of the mobile web. They direct a heavy expertise of mobile software & hardware as well as mobile usability. Currently a quick & high divided developement underlies the age of mobile technology. The cooperation with external services ensures that the e-shop always offers up-to-date mobile content.		Furthermore, this mobile API enables an external management service to finally configure the mobile content. Such an external service is mostly a company that is primarily specializing in concerns of the mobile web. They direct a heavy expertise of mobile software & hardware as well as mobile usability. Currently a quick & high divided developement underlies the age of the mobile technology. The cooperation with such external services ensures that the e-shop always offers up-to-date mobile content.

	Finally the request of a mobile device to the URL of an e-shop enables the application framework to chek out the relevant technical information ~~specific type of that device as well as..~~. In the ~~right~~ figure~~... t.b.d~~.		Finally the request of a mobile device to the URL of an e-shop enables the application framework to chek out the relevant technical information. As you can see in the figure, the redirection to the mobile page passes the management service & the mobile content can be processed back to the requesting device.

	[[Image:Process-of-a-mobile-request.jpg\|right\|thumb\|300px\|The Process of a Mobile Request]]		[[Image:Process-of-a-mobile-request.jpg\|right\|thumb\|300px\|The Process of a Mobile Request]]

Michaa: /* Technical Realization */

2011-08-07T13:50:25Z

Technical Realization

← Older revision		Revision as of 13:50, 7 August 2011
Line 76:		Line 76:

	==Technical Realization==		==Technical Realization==

			The setup of the visual interface has to be implemented via the application framework of the specific e-shop software. Therefore the application framework provides a so called mobile application programming interface (short: mobile API). This mobile API threads the necessary content information for every single request of a mobile device. A markup language (e.g. HTML5) predefines the layout of the requested mobile page.

			Furthermore, this mobile API enables an external management service to finally configure the mobile content. Such an external service is mostly a company that is primarily specializing in concerns of the mobile web. They direct a heavy expertise of mobile software & hardware as well as mobile usability. Currently a quick & high divided developement underlies the age of mobile technology. The cooperation with external services ensures that the e-shop always offers up-to-date mobile content.

			Finally the request of a mobile device to the URL of an e-shop enables the application framework to chek out the relevant technical information specific type of that device as well as... In the right figure... t.b.d.

	[[Image:Process-of-a-mobile-request.jpg\|right\|thumb\|300px\|The Process of a Mobile Request]]		[[Image:Process-of-a-mobile-request.jpg\|right\|thumb\|300px\|The Process of a Mobile Request]]
	The setup of the visual interface has to be implemented via the application framework of the specific e-shop software. Therefore the application framework provides a so called mobile application programming interface (short: mobile API). This mobile API threads the necessary content information for every single request of a mobile device. A markup language (e.g. HTML5) predefines the layout of the requested mobile page.
	Furthermore, this mobile API enables an external management service to finally configure the mobile content. Such an external service is mostly a company that is primarily specializing in concerns of the mobile web. They direct a heavy expertise of mobile software & hardware as well as mobile usability. Currently a quick & high divided developement underlies the age of mobile technology. The cooperation with external service ensures that the e-shop always offers up-to-date mobile content.

Michaa: /* Technical Realization */

2011-08-07T13:43:16Z

Technical Realization

← Older revision		Revision as of 13:43, 7 August 2011
Line 78:		Line 78:

	[[Image:Process-of-a-mobile-request.jpg\|right\|thumb\|300px\|The Process of a Mobile Request]]		[[Image:Process-of-a-mobile-request.jpg\|right\|thumb\|300px\|The Process of a Mobile Request]]
	The setup of the visual interface has to be implemented via the application framework of the specific e-shop software. Therefore the application framework provides a so called mobile application programming interface (short: mobile API). This mobile API threads the necessary content information for every single request of a mobile device. A markup language (e.g. HTML5) predefines the layout of the requested mobile page. Furthermore, this mobile API enables an external management service to finally configure the mobile content. Such an external service is ~~needed for~~ the		The setup of the visual interface has to be implemented via the application framework of the specific e-shop software. Therefore the application framework provides a so called mobile application programming interface (short: mobile API). This mobile API threads the necessary content information for every single request of a mobile device. A markup language (e.g. HTML5) predefines the layout of the requested mobile page.
			Furthermore, this mobile API enables an external management service to finally configure the mobile content. Such an external service is mostly a company that is primarily specializing in concerns of the mobile web. They direct a heavy expertise of mobile software & hardware as well as mobile usability. Currently a quick & high divided developement underlies the age of mobile technology. The cooperation with external service ensures that the e-shop always offers up-to-date mobile content.

Michaa: /* Technical Realization */

2011-08-07T13:26:25Z

Technical Realization

← Older revision		Revision as of 13:26, 7 August 2011
Line 77:		Line 77:
	==Technical Realization==		==Technical Realization==

	[[Image:Process-of-a-mobile-request.jpg\|~~left~~\|thumb\|300px\|The Process of a Mobile Request]]		[[Image:Process-of-a-mobile-request.jpg\|right\|thumb\|300px\|The Process of a Mobile Request]]
	t.b.d.		The setup of the visual interface has to be implemented via the application framework of the specific e-shop software. Therefore the application framework provides a so called mobile application programming interface (short: mobile API). This mobile API threads the necessary content information for every single request of a mobile device. A markup language (e.g. HTML5) predefines the layout of the requested mobile page. Furthermore, this mobile API enables an external management service to finally configure the mobile content. Such an external service is needed for the

Michaa: /* Introduction */

2011-08-02T07:51:39Z

Introduction

← Older revision		Revision as of 07:51, 2 August 2011
Line 3:		Line 3:
	The mobile age is as well a challenge for commercial websites to provide e.g. an e-shop running compatible on different mobile devices. See also [[wikipedia:M-commerce]] !		The mobile age is as well a challenge for commercial websites to provide e.g. an e-shop running compatible on different mobile devices. See also [[wikipedia:M-commerce]] !

	Retailers are faced with a wide range of various hardware & software conditions. First of all, they have to decide between web or native applications. ~~All these~~ app types keep different advantages & disadvantages. A native shopping app is on the one hand more expansive to build up than a web shopping app. On the other hand a native app allows to use more features of a given device in comparison to a web app. A web app is platform indepentent but mostly doesn't ensure such a high user expierence like a native app.		Retailers are faced with a wide range of various hardware & software conditions. First of all, they have to decide between web or native applications. These two app types keep different advantages & disadvantages. A native shopping app is on the one hand more expansive to build up than a web shopping app. On the other hand a native app allows to use more features of a given device in comparison to a web app. A web app is platform indepentent but mostly doesn't ensure such a high user expierence like a native app.

	Online retailers have to managage a huge amount of data (product catalogues, customers's information, supplier specificatons etc.) via their shop software. Additionally, they have to assure the security of all electronically safed data. This has to be valid for their mobile applications, too.		Online retailers have to managage a huge amount of data (product catalogues, customers's information, supplier specificatons etc.) via their shop software. Additionally, they have to assure the security of all electronically safed data. This has to be valid for their mobile applications, too.

Michaa: /* Technical Realization */

2011-08-01T15:01:27Z

Technical Realization

← Older revision		Revision as of 15:01, 1 August 2011
Line 77:		Line 77:
	==Technical Realization==		==Technical Realization==

			[[Image:Process-of-a-mobile-request.jpg\|left\|thumb\|300px\|The Process of a Mobile Request]]
	t.b.d.		t.b.d.

Michaa: /* First Mockup */

2011-08-01T14:46:21Z

First Mockup

← Older revision		Revision as of 14:46, 1 August 2011
Line 22:		Line 22:
	</gallery>		</gallery>

	After creating a first visual layout I've uploaded and fitted a simple image ~~oline~~ in order to get a first impression over an iPhone. I discussed this first result with several people. My discussion criterias concerned particularly the following questions:		After creating a first visual layout I've uploaded and fitted a simple image online in order to get a first impression over an iPhone. I discussed this first result with several people. My discussion criterias concerned particularly the following questions:
	*Is the concept of a fixed header & footer useful?		*Is the concept of a fixed header & footer useful?
	*Are the sizes of fonts, images or icons visible for all users (as well for people who wear glasses)?		*Are the sizes of fonts, images or icons visible for all users (as well for people who wear glasses)?