The Existing Cordova Application: EventApp
This is a part of a blog series. In this blog I am describing an old solution and its architecture. This is not the recommended way to build mobile solutions today anymore. Towards the end of the blog series we are showcasing how to build state of the art mobile solutions today.
The EventApp, discussed in this blog, was developed as a mobile solution to replace printed catalogs and brochures. It gives the event organizers the capability to distribute information about future present and past events fast with features like survey or report, and agenda. Additionally, attendees have centralised reference to all information rather than searching through different locations for details about events and sessions along with other information. Attendees can assign sessions to themselves and view them to manage their schedules. This hybrid app was implemented using the old SAP Cloud Platform SDK based on Cordova, giving users mobile access to the described features.
EventApp UI Design
The app consists of several pages to display the information.
A menu bar, as represented in figure 1, allows to navigate inside the app. The menu shows information about the chosen event such as assigned session, session list, and speaker. In the General section, users can access pages displaying their profile, messages, and preferences to alter application related settings.
Figure 1: Cordova EventApp’s Menu Bar
The event list page displays all public events as well as the ones to which the user has been invited. Names and primary information of events help users to choose the correct one.
Figure 2: Cordova EventApp’s Event List Page
After choosing an event from the event list, a page will be shown to display an overview of the event. The details include the start and end date, location, and a short description of this event are shown on this page.
The session list can be found on the next main page of this app to present all sessions of an event with the capability to navigate to them. A button located near the primitive session information, allows the user to add it to the user’s agenda.
Figure 3: Cordova EventApp’s Event Overview Page.
Figure 4: Cordova EventApp’s Session List Page.
There are various other pages of this app which we skip the detail description to keep this simple.
The entity data model, Figure 5, consists of twenty-seven tables to host all events’ information. The event table is acknowledged as the primary table and so is connected directly or indirectly to the other tables. This data model design demands the dependency of tables on the event table.
The EventApp service uses the OData protocol to implement a REST architecture.
Figure 5: EventApp Data Entity Model.
A Complex cross platform mobile solution build using a OData backend and SAP Mobile Services to enable attendees to access data on events.