Implement a prototype interactive map based interface to information about points of interest in Quakertown. This should
Posted: Thu Jul 14, 2022 2:18 pm
Implement a prototype interactive map based interface toinformation about points of interest in Quakertown. This should bea web based interface using HTML, CSS, and JS and does not requirea database backend. Build your prototype based on your design formthe first part of the module and feel free to rely on the graphics,maps, and textual content from the Google Drive mock-ups. You needto include all the points of interest listed in the Google Drive.You can add points based on your research, but need to keep theoriginal defined points. I recommend using standardizedgraphics/icons from the Google Drive to support your prototype, butyou can create your own graphics or icons if time, interest, anddesign allow.
The prototype should be functional from a traditionaldesktop/laptop browser that does not have to be at the physicallocation of the current park as well as funtional via a locationaware mobile device. You do NOT need to go to the park to testlocation triggers. Use GPS locations around your home to testlocation based triggers. Specific GPS coordinates for the park canbe swapped out later. YOur prototype will be test by you and yourpartneer, so use GPS coordinates local to you all for that purpose.The code from the shared repository should demonstrate how theGeolocation API polls current coordinates from GPS enabled mobiledevices, so you can harvest GPS coordinates around you, orimplement some of the sample code from placeslike https://www.w3schools.com/html/html5_geolocation.asp (Linksto an external site.) or other examples on the Internet toexperiment, harvest coordinates, and test/create funtionality.
Your prototype should implement accessible and usablecode/design. Test it with a screen reader on your laptop/desktop ormobile device and look for those common issues like alt text,semantic structure, and descriptive link text. Watch load time andthe ability to adapt to different screen sizes. Do not rely onabsolute links as they can cause problems when transferring yoursite. Be sure you and your partner test the prototype on your ownmachines to ensure the relative links work properly.
The prototype should be functional from a traditionaldesktop/laptop browser that does not have to be at the physicallocation of the current park as well as funtional via a locationaware mobile device. You do NOT need to go to the park to testlocation triggers. Use GPS locations around your home to testlocation based triggers. Specific GPS coordinates for the park canbe swapped out later. YOur prototype will be test by you and yourpartneer, so use GPS coordinates local to you all for that purpose.The code from the shared repository should demonstrate how theGeolocation API polls current coordinates from GPS enabled mobiledevices, so you can harvest GPS coordinates around you, orimplement some of the sample code from placeslike https://www.w3schools.com/html/html5_geolocation.asp (Linksto an external site.) or other examples on the Internet toexperiment, harvest coordinates, and test/create funtionality.
Your prototype should implement accessible and usablecode/design. Test it with a screen reader on your laptop/desktop ormobile device and look for those common issues like alt text,semantic structure, and descriptive link text. Watch load time andthe ability to adapt to different screen sizes. Do not rely onabsolute links as they can cause problems when transferring yoursite. Be sure you and your partner test the prototype on your ownmachines to ensure the relative links work properly.