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