PhoneGap allows developers to work with essentially the same tools (HTML, CSS, and JavaScript) used for creating and maintaining websites. When Adobe supported the PhoneGap framework, an installation file would be downloaded which made the setup process simple. However, Adobe announced discontinuance of PhoneGap as of October 1, 2020 (see www.phonegap.com/start). PhoneGap is now a free and open source, but unsupported product. This makes our usage and preview of PhoneGap this week somewhat limited. I want to again start with the user interface for building (simulate building) a PhoneGap application (see pp. 330-331). The requirements for this Derby app is to provide two screens; one that lists all of the teams/leagues and one that lists all the players. When a league/team is selected, the application shows the roster (screen) for the team. When a player is selected, it shows which team (screen) the player belongs to and his/her number.For our assignment this week ( Assignment 5), you will need to simulate two screens/interfaces; one screen list the Derby teams/header added ( Figure 11:29, p. 334 bottom) and one screen list is a Derby roster search/header added ( Figure 11:30, p. 335 bottom) – refer to our previous lesson on User Interface Design, chapter 4, also see a YouTube video in this week’s Learning Materials on using Figma for modeling. There must be navigation between these screens/pages. With PhoneGap every screen is another HTML page. So you will create your screens as HTML pages then embed the necessary UI elements onto the screen/page. On a website, the “index file” holds the HTML content for the main page. Different tags (head, anchor, page, Div, numbered and unnumbered list, etc.) are wrapped within HTML/BODY code to give the page its features and functionality. Cascade Style Sheets (CSS) can be embodied within the HTML to give dynamic customization/style to pages, and JavaScripts provide animation or interactive functions. Our authors provide examples of HTML script, CSS and useful JavaScript Libraries from which you can leverage for your understanding and simulation. Your goal is to:
- Download and install Figma (can use comparable SW of your choice) on your computer. This is same as used in previous simulation assignments.
- Model each screen using Figma – from the Figma widgets/icons library, select figures (circles, rectangles, ovals, call-outs, etc) to represent the UI elements needed for your two screens,
- Place these figures onto a two design canvas that reflect the two screens that you are modelling.
Make one screen shot here that shows you have install the Figma modelling/wireframing tool (or a comparable tool of your choice) and did some modelling* You are ready to start simulating your app (two screens/interfaces that match Figure 11:29 and Figire 11:30 above). First, state what platform (iOS, Android, Windows, etc.) you are simulating.
- Select two mobile app templates appropriate for the platform that you are simulating – one for each prototype screen.
- From the Figma widgets/icons library convert figures from your model; carefully size and position these as UI elements (icons, Button, View, Tablelayout, etc.) that follow the (Figure 11:29, p.334) – list of Derby teams (first prototype screen)
- From the Figma widgets/icons library convert figures from your model and carefully size and position as UI elements (icons, Button, View, Tablelayout, etc.) that follows the (Figure 11:30, p.335) – a Derby roster search (second prototype screen)
- Place each of your prototype screens onto a mobile app template that you selected above. (I suggest here that you identify/label EACH UI element used on each prototype screen)
Make a second screen shot here that shows two screens with placement of UI content provided by HTML, CSS, and JavaScript (this is your simulated mobile app)Your app is using HTML, CSS, and JavaScript coding, but must conform to native features for whatever platform you are simulating. Write an explanation for each UI element that you used – that provides functionality for your mobile app; mostly ( HTML, CSS, and/or JavaScript) (No coding; just explanations required).* Remember with PhoneGap each screen is an html page/screen (a UI element); UI elements are generated and embedd within each screen using HTML, JavaScripts,and CSS to achieve the native platform look/feel. Also remember – ensure that the JavaScript function onDeviceReady is fired (p.324)
- For your first prototype screen – list of Derby teams, explain Each UI element describing what/how it gives functionality to your simulated app. Hint: there must be a scroller, a query, and storage function like lawnchair in order for this to work.
- For your second prototype screen – a Derby roster search, explain Each UI element describing what/how it gives functionality to your simulated app. Hint: need a textbox, a search button and onDeviceReady function.
- Describe/explain 4 principles of mobile interface design that are employed in your simulated app (see chapter 4 and the article: “Principles of mobile interface design” left in this week’s Learning Materials section
- Explain native features that are peculiar – must exist for the platform you are simulationg (example: BackStack and 4 fundamentals for Android; basic functions of iOS apps (see chapter 6 – Androd; chapter 7 – IOS).
When you are ready to post, click the Week 13 – Assignment 5 (Building (simulating) a Derby app with PhoneGap) assignment link, then Either click the ” Write Submission” link and directly paste your screen shots into this assignment box OR Browse your Computer and add the entire Microsoft Word document as an attachment (Mac users, please remember to append the “.docx” extension to the filename).
