After South Australia

[keithamoss]

• Did Add Stall close down automatically at 8pm on election day?
• Check the raw access logs for the API
• Write requirements for the Twitter GUI with H
• Handle nuking all of those spammy links so they actually 404/301 never was here
• What to do about basemaps for the next Federal? Finding a balance between basemap and geocoding services could be tricky. (How does Carto measure page views in their 75k limit?)
• How can we get to event value in GA?

General Bug Fixes

• Find a better fix for the GeoJSON not always loading issue

UI Fixes

• Fix the main UI containers so they only fill 100% and take up the proper amount of space
• Find a better fix for the Fruit phone BottomNav gap issues (Safari Responsive Design Mode ftw)
• page-content on iPhone 5S (Chrome) doesn't include the bottom padding to allow scrolling down. (Hackily fixed for now by adding 100px of padding to the bottom of all pages.)
• Better flag errors on AddStall (e.g. Failing to provide Contact mail)
• LGG3 doesn't appear to load Roboto

SEO

• What can we do with server-side rendering or similar to make it more Crawler friendly? Is there a simpler approach? Is it even required these days?
• Submit a sitemap to Google et al.
• Investigate SEO tweaks - we're not even on the first page of Bing

For Consideration

• What could go on the Admin Console homepage that would be useful to see? (Alternatively, default to an existing page)
• Did we ever load that public school dataset?
• During polling place loading, what happens if there's a difference in two historical data points?
• Would a "View on map" option be useful on Finder and PollingPlaceQuerying?
• New feature idea: Let me know when there are stalls available near me. For people in the lead-up - either tell them election eve or election morning. Email or notification. Look at traffic patterns and events prior to validate.

New Features

• Filter to find vegan et cetera
• A place to show images et cetera that we want to highlight (per election? per polling place?)

UI Enhancements

• Include more prominent calls to action to:
  • Submit booths in the critical pre-election period (form-based)
  • Report booths on election day
  • Look at our Redbubble!
• Think about how we can add clearer call to action when users discover a stall. The message is passive at the moment.
  • Think about how we can use the high/med/low chance of sausage as a prompt for submissions. Think about how we can better engage and prompt users like "Do you know about this stall?" "Can you help with this stall?" Maybe link to a "How to help us collect data" guide (Talk to P&Cs, Google)
• Revamp the design of PollingPlaceCardMini. Stalls without info overshadow those with. (c.f. Google's Election Site) and the expander icon takes a lot of space on those without stuff to expand (ideally, let's have nothing to show that needs an expander). Also, show some historical information about the booth would be nice. Also, we may have photo(s) to show from this election (or even past?). Also maybe color-coding by has food/has nothing/is unknown. Make the Red Cross of Shame clearer (it's just an icon at the moment).
• Think about adding a nudge banner (see SausageMap.tsx) to the Map and/or Finder to prompt users to use their GPS. (Depending on results of interactions with the current GPS mechanism from the last elections)
  • c.f. https://developers.google.com/web/fundamentals/native-hardware/user-location/#gently_nudge_users_to_grant_permission_to_their_location, https://uxplanet.org/mobile-ux-design-the-right-ways-to-ask-users-for-permissions-6cdd9ab25c27, https://material.io/guidelines/patterns/permissions.html#permissions-request-patterns
• Should stall have unique URLs on public and a Share button with that fancy thing like The Sizzle has?

Refactoring

• Run Lighthouse - take any quick wins and log the rest as issues if they warrant attention (check GA page timings to corroborate)
• Integrate LogRocket to get screenshots when errors occur (ref)
• Can we reduce the JS size without going full code splitting? (OpenLayers - are we including it all or is tree shaking working? Would vendor/app bundles with async loading help wrt. caching?)
• Investigate switching geocoding to Mapbox and whether we can use their directions APIs for what we wanted to do for finding polling places.
  • Do we have to use their basemap if we use their APIs?
  • Did enough people seem to use Finder to warrant it?
• Better share common code between admin and public
• Think about how we can host the API for free/<= $5/month in a better place (c.f. security, moving to a better language, automatic db backups). But probably don't rewrite it or re-engineer with PostGIS. The time to do so and re-test everything (or write tests) isn't worth it at this point.

AB#101