133
edits
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. | ||
edits