letsdoitworld / world-cleanup-day Goto Github PK

The project currently uses the expo sdk version 19.0.0. According to their release announcement, there are no breaking changes.
However, the new version uses a different version of react-native, and it should be investigated.

Also, it might fix issues with the ImagePicker on lower versions of android ( 4.4 )

At the moment, in My activity, only the trashpoint created by the current user are displayed. The trashpoints edited by the current user should be displayed in My activity as well

If you look at the Oslo data or the Belgian 4, you have to tap too many times to get anywhere. The Belgian example zooms you in to an absurd level before the cluster is split. Could be duplicated reports, but the Oslo data also makes it obvious.

Starting with zoomed out Europe, I see a cluster of 15 over Norway. I have to click it some 7 times before it is split into subclusters. I expected to be taken to that zoom level immediately, upon first click.

As a sidenote, related to #5, the cluster position keeps jumping around on the map when you're zooming.

After photo is added and user is directed to add more information page, it is common to get a network error message on some phones (Samsung S6 Edge, android 7.1.1; Sony Xperia f5321, android 7.1.1)

Make it super easy to understand (and for Google to find) what APIs exist and how to use them + some showcase examples of apps using them.

logo files are here https://letsdoitworld-my.sharepoint.com/personal/ldiw_letsdoitworld_org/_layouts/15/onedrive.aspx?id=%2Fpersonal%2Fldiw%5Fletsdoitworld%5Forg%2FDocuments%2FWCUD%202018%20Marketing%20materials%2FLogos&FolderCTID=0x0120006EB08C8FDD89814FA97F25EDA468D580

everywhere have to be full logo

regular app users can currently delete all photos and it is not needed function

When creating a trashpoint, if there is no Internet connection, keep the data locally until it can be sent to the database. Display the user a message: Your trashpoint is going to be created when your device is connected to the Internet

Sign-up should be available through e-mail/phone:

1. security reasons
2. if user doesnt have accounts

User 1: Sony Xperia XZs (sw android 7.1.1) - installed the app on 9.09.

Document mandatory and nice-to-have app features and add relevant wireframes, mockups and design images to each.

Video
https://drive.google.com/file/d/0B5mTVq-3n9jhWU54R2RoSW8zaHc/view

Trashpoint clustering means displaying multiple nearby trashpoints as a single marker on the map. This helps to unclutter the view when zoomed out and/or large viewports.

The current trashpoint implementation uses 30 rectangular grids with cell size ranging from 1m to 1000km. The trashpoints are mapped to grid coordinates using CouchDB views. Each grid cell has a status (derived from the most urgent status among the trahspoints in it), a trashpoint count, and a position (at the center of the grid cell). The API endpoint GET /overview/clusters transforms the viewpoirt rectangle from longitude/latitude coordinates to grid coordinates, to determine which grid cells should be displayed. The frontend clients are the ones that decide which grid size to request depending on zoom.

The issue: placing the cluster at the center of the grid cell leads to cases where there is a visible discrepancy between the location of most trashpoints in the cell and the location of the cluster.

Possible solutions:

1. Make the frontend clients request smaller grid sizes. The current grid sizes have been chosen to be "human readable" (multiples of common sizes), but better sizes can be calculated by picking distances that map to ~1mm on the device screen at a certain zoom level, thus making the displacement mostly undetectable by the user. Please note that the mapping of the trashpoints to the grid is done with CouchDB views, which has two implications: (a) every new grid view needs to be calculated, which may take a while, depending on how many trashpoints there are, and (b) the grid size of a view cannot by dynamic, it is hardcoded in the view's map function, so we need to pick grid sizes that work well with most devices, we cannot request device-specific grids.
2. Change the cluster placement logic. For simplicity's sake, the cluster position was chosen to always be the center of the grid cell in the reduce functions of the CouchDB views. However, these functions have access to the coordinates of all the trashpoints in the cell, so a better algorithm is possible, as long as it can be implemented in vanilla JS with only the SpiderMonkey engine primitives (Math etc.). A very rudimentary improvement would be to use the center of the bounding box containing all trashpoints, but of course a more advanced algorithm using distribution weights would be even better.

Add cleaned button in initial “point status.” Normally, when picking up a handful to bagful of litter, I remove the litter. This is also important to capture all the information on the litter during the first pass. If the average user must go back to document that they picked up, they won’t do it. To me “regular” and “threat” describe the type of trash. “Cleaned” describes my actions.

From #58 Display a section in the user profile where the volunteer can send an application to the area leader/s that are able to manage his account. The area leader has a section where he sees the list of applications. After the request is solved, area leaders or super admins can dismiss the request which disappears from the list

Idea is to organise mapping event on 9th of Nov in Amsterdam and allow global admin to see the results. Team name is not visible on trash point ID card

If I navigate on the map, I should be allowed to place a pin on the map manually, without first pressing the "add" button. More intuitivity is rather good.

Mandatory photo should be added only when creating TP and when marking it as cleaned. For example if you're only adding a new hashtag and save there's no sense to ask for a new photo.

"Estonian product, sponsored by the country and government" to be added to the app About field

When i don't want to save a TP and press back (instead of cancel). Samsung S6 Edge, Android 7.1.1. Force stop in app settings is the only fix

• Background looping video
• Align Terms & Conditions and Privacy Policy to bottom
• increase space between buttons and tryout link

Map should follow the user automatically

• icons
• text
• left design vs right app

Status.io is a good candidate:
https://status.io/

Examples:
http://status.crowdin.com/
https://status.status.io/

Trash captured - reduce time on this screen from appx 5 seconds to 2 seconds.

When adding a spot while not being at the place, I should be able to choose a previous photo. Even for the people who are used to take a photo first, this is more intuitive.