problem: people want to quickly find a particular store even if they are not nearby

solution: add favourites and render these at the top of the list or add a tab or something. User cookies or something so that sign in is not required.

problem: some people add duplicate stores because they don't notice that their store is already there.

solution: if the user is within 100 meters of an existing store, ask them the existing listing is the right one.

problem: no link to github

solution: since there's no real need for a side menu, just replace the menu with a tabbar (https://onsen.io/v2/api/react/Tabbar.html), add an icon for home, github, and feedback (from #31 )

We need to be careful that interface updates don't discard useful information.

Great work, thanks for being the person who did something useful with an idea!

I'd love the ability to mark a few stores as favorites. To continue with the concept of not using logins, the favourite information can be stored in a cookie.

You would then need a way of doing something with the favourite info, such as making the favorites appear at the top of the list on first-open/if no location was searched for, or a tab/toggle to just show favourites.

Keep up the good work!

problem: users can't complain about app

solution: add a complaints/suggestion/feedback form

problem: no database backups being taken

Problem: users cannot add a status to an existing location

solution: detect users location and list nearest places, let them select from a list

Problem: project structure needs to improve
For example - in ui directory, pages and layout are in same directory.

Solution: we can update file structure and code structure to better understanding. also we can divide components in to separate files, so it can be reusable.
Also we can move client and server startup parts in imports.

problem: line under search box is misplaced while scroll down, as no need to stick border line for search box

Solution: set border to content instead of search box, so can't stick always while scrolling window

problem: not all members are public

This is a personal choice but it's usually a good idea for members of the github organisation public. It sets the tone for an open culture as more people start getting involved.

You can make yourself public by going to https://github.com/orgs/howlongistheline/people and changing the setting next to your name to public.

Anyone who contributes to the project should be invited to become a member of the organisation as it makes certain things easier (increased privileges etc). You can also see any pending invitations here: https://github.com/orgs/howlongistheline/people/pending_invitations

ping
@olliechick
@jimkleine
@ioioio8888

problem: some people are adding stores in the wrong location.

solution: when a user tries to update the line status but a location failure occurs, allow them to change the store coordinates to their current location.

The search field is becoming laggy, even on relatively capable devices e.g. iPad Air. Possibly related to:

1. An increasing number of stores in the DB vs the current Search bar behaviour of incrementally filtering candidates as you type (I'm seeing a lag in character display in the search bar); or

2. More client processing of live status updates during filtering (is the slider UI more intensive in this regard? Could status updates be deferred during active filtering?)

problem: there's no preview on social media when sharing the site

If location services are not enabled (or the browser's Share location? Request is denied), a pop-up appears ("Cant get the location ..."; message is missing the apostrophe). That behaviour is working correctly, but the animated "Getting your location" should hide itself at that point.

solution: Auto-hide "Getting your location" pane if location services are not available.

problem: not showing exact numbers in line slider, while updating or done any movements on slider, it showing number of people after page refresh.

Solution: when need to change line, need to show slider position (in tooltip), with what will be result after updating.

Possible Solution:
Upgrade kind-of to version 6.0.3 or later.

problem: fetching geolocation can be very slow

After submitting the data to add a new shop, the geolocation can take a long time.

Solution: fetch the location using async upon loading the route. Use await to show the user that the browser is trying to find their location in the background.

The domain (only) cert is being served, even when the www URL is accessed. You should add www.howlongistheline.org to the LetsEncrypt cert as a Subject Alternate Name (SAN).

problem: users can't upload pictures when updating the status.

solution: implement optional image upload on the status update view and use filestack.com (or whatever) to serve the images so that the server instance doesn't need to store any data.

1. One class of people best placed to keep the line status regularly updated is the door security folks, however the current "busy" status of "Busy. Stay Home." might not be acceptable for store staff to select (the "Stay Home" part).
2. While trying to update line statuses today, I was offered two different criteria at two different stores (one said more than six; the other said more than 20). We should be clear how long the queue potentially is for people, so they can make an informed decision about whether they will wait e.g. Busy (>6) or Busy (>20), or even a fourth status of Very Busy (>20) (much beyond this gets difficult to count with a queue that may be moving).
3. This factors into the store "size" problem. Of the two similar-sized queues at two supermarkets I observed this afternoon, one was moving significantly faster than the other. Curiously, the faster moving queue was at the smaller of the two stores. The critical element for shoppers is how long the wait time is, not necessarily the number of people in the queue, but we are currently using the latter as a proxy for the former.

problem: people want to show off their additions and update stats

solution: implement user accounts so that stats can be tracked, create a basic profile page and profile ranking (based on additions and updates).

problem: many coordinates are wrong (added incorrectly). This prevents other users from updating the status.

solution: instead of the toaster notification, send users to a view with:

Error: are you really at this location? It appears that either you are not at the shop, or we have the wrong coordinates for the shop.

If you are not at this shop right now: ask your friends on facebook etc to update this shop for you whenever they go.

If you are at this shop right now, please tap to reset the location.

Set the coordinates to the users coordinates, and append the existing coordinates to historical data.

When checking the users location matches the store, check historical coordinates too, and if any are a match let them update it.

problem: lines move at different speeds and this makes the same line numbers mean different things at different stores.

solution: allow users to add the number of checkouts available in store.

problem: adding status update using dropdown is annoying

solution: change the dropdown to radio buttons

problem: dropdown is annoying for users

solution: change to radio buttons

1. There is a typo in the "location" bar: "getting your location" should probably be "Getting your location ..."
2. The Search bar shouldn't have a red background colour: red should be reserved for errors etc.
   I appreciate that this is to highlight the search bar, but coloured backgrounds in text boxes can also present contrast issues that result in a need to "invert" the text colour e.g. white on blue etc. Would a coloured border be better? Some look and feel examples here: https://mdbootstrap.com/docs/jquery/forms/search/

problem: when user has location disabled it fails without error

We already have a modest international following, so we can no longer rely on being able to perform maintenance outside of NZ store trading hours. Can we use a GeoIP database or similar to automatically populate a store country field (to keep this low impact from the user's pespective)?

I visited 4 local supermarkets (I'm a cyclist) this afternoon to update queues, add new stores and hand out posters to the door security staff. Using Firefox on Android. I was able to add two stores without issue (GetFresh Mangere and Countdown Mangere Town Centre), but I was refused access to update the queue status at the two existing stores (Pak n Save Mangere and Countdown Auckland Airport) "Are you really at this store?". I recorded decimal GPS locations for each of the two stores so that we can identify whether this is a bad data or a location logic problem:

1. Pak N Save Mangere: -36.96827783, 174.79745184
2. Countdown Auckland Airport: -36.99765505, 174.78860649

problem: people still adding duplicate stores

solution: when adding a new store, automatically search existing stores as the user types, and display it to the user.

How to Add a Shop 101

1. Stay safe –
   a. Wear a mask or homemade face covering if you are going out on foot. The science is in on masks they serve as a barrier to virus transmission.
   b. You can add shops from the relative safety of your car – so don’t be afraid to drive up close to the entry in a loading zone to add the store. This should take a minute or two not much longer so you likely won’t have to worry about loading zone concerns.

2. Check to ensure your GPS on your browsers is enabled – this is usually in the privacy settings.

3. Only add shops if you are physically there – check the maps application on your phone google maps or apple maps to ensure that your device is pinging directly at the store.
   a. Sometimes this may require a bit of patience depending on your signal and connection quality.
   b. Copy and paste the address of the shop from your maps tool and load it into the table below the shop name on the shop submission page.

4. The app is programmed to detect around 100 meters of wherever the shop is added from.
   a. This means if someone has added the shop from the other side of the parking lot – that original upload point is what is captured as the shop. So please add locations as close to the main door as possible.

@jimkleine @olliechick there is a group here: https://www.facebook.com/groups/1161156860891990/?fref=nf

Let me know if you join so I can add you as an admin.

problem: users see oldest comments first, but they want to see the most recent comments first because the latest information is most important.

problem: location is updated after returning to / route from other views. This makes the user wait more than they really need.

solution: store users location for x minutes (5?) as a persistent variable and also add a manual refresh button.

problem: people can't add things that are out of stock

People want to be able to add things that are out of stock but are unable to.

problem: stores do not have opening hours and there's no status for "store closed".

solution: allow people to add opening hours, get store time zone from location coordinates

There is a missing ">" on the </title> end tag.

solution: Fix typo

problem: there are many duplicate stores

solution: allow users to remove duplicate stores:

1. add a button to the card rendered for each store "this is a duplicate" or something
2. create a new view where users can select all the other store objects that are referring to the same location (all the duplicates)
3. Take all the data (name, address, coordinates) from all the duplicates. Ask the user which data is best, and combine these into a new object. So, which name is best, which address is best, and which coordinates are best (show a map for each, use openstreetmap).
4. archive all the duplicates into the archived collection.

problem: places and status are stored on same object. This means that when a status is updated it replaces the location object.

solution: store locations (shops etc) in its own collection.

problem: can't share the status of a store

People want to be able to share the status of an individual store on facebook, but they can't.

The old UI coloured the queue status green/orange/red for a quick visual indication. I'm aware we are making somewhat arbitrary choices re queue depth at this point, but 0 should be green, 50+ should be red and we need to nominate "breakpoints" for green/orange and orange/red boundaries.

solution: Colour the queue description text ("There were nn people in line ...") and or slider control (the latter might be more tricky, since it is an interactive control).

problem: no validation on user location before updating status

solution: check that user is within x meters of the shop location before allowing them to make an update.

Problem: users cannot add the address for a new location

solution: provide an option for users to add a new location (related to #5) if the location they are currently at is not listed. Ask them to paste in the full official address given on the store's website or google maps.

problem: some stores have different capacity to others so the lines move at different speeds.

possible solution: add a capacity metric and allow users to add more fine grained details to now many people are in line

problem: search not implemented on /nearme

/nearme is a new view to refine all the good stuff from Index.jsx and also implement a new way of fetching data from mongodb (there are too many objects to just send everything to the client now).

This is intended to replace Index.jsx as the / route when all the bugs are gone.