melton-foundation / melton-app-client-flutter Goto Github PK

This has a dependency on the backend implementing a no-auth version of /posts

See melton-foundation/Melton-App-Server#58 for all details.

Would need to use third-party service, preferably something that's free for self hosting.
Probably would not need any change in the backend Django code

Add your name when you raise your first PR

A way for a user to paste in an appToken which gets stored.

This is useful when troubleshooting or google oauth is causing issues (eg for Chinese Fellows)

If implementing this, consider the appToken while letting in users and make Gauth sign-in non-mandatory.
(Currently both are needed for successful auth. to app's features)

Suggested spot: put it under the vertical ellipsis on the app bar top right, along with things like about/privacy policy

Directory already changes number of preview cards per row based on orientation.

Test other parts of app and improve responsive design.

Especially on tablet size devices.

In landscape mode, users can't see buttons to "Sign up" or "Close" (for the "who are you" error screen)

A smaller font is chosen for names longer than 20 chars.
But names longer than about 25 chars still are not fitting in the Fellow Info Box

Currently, avoidable API calls are:

1. /profile to check token validity on login and again /profile called to load first screen of app if token is valid

2. posts full page preview calls /posts endpoint even though home screen preview of top 3 most recent posts calls /posts

Links specified in the markdown of "posts" articles should ideally open an in-app webview.
While this works very nicely on iOS with forceSafariVC set to true, on Android the default webview is not really nice.
We tried to improve it by enabling JS and allowing HTTP links in #34, but there's no progress indicator for the page load and no way to copy link (to open in browser).

So until we implement a simple Webview for Android (reusable even in iOS, if decent enough), let's just force Android Markdown links to open in the default browser.

The options in world_cities.dart are taken from simplemaps (free, smaller version of the database).
Only the cities with more than 100,000 population have been chosen. For cities with a common name (in ASCII) and a common country, the city with higher population is chosen.

This can lead to some confusion, esp. in the US, which has multiple states with the same city name.

The workaround is to choose your city in the dropdown (say Gainesville, United States) and check the map to see if we're putting you in Gainesville, FL or Gainesville, GA (spoiler alert: it's Georgia).

Then you'd have to fall back to searching for the nearest city which is included in the list, which is made hard by the fact that many US cities have been included, with no state, so you can't search by your state.

Currently it's quite long before it declares invalid token or no internet

API/backend treats Users as case-sensitive, so signing-up with "[email protected]" and signing-in with "[email protected]" will fail.

This is made worse by the autocorrect casing edits of phones, which can capitalize the first letter without the user noticing it.

URL links and send mail features are not working in android 11

Instead of just showing the alert and - when it's dismissed - making the user dismiss the sign up page manually.

Currently we are switching between a font size of 20 and 14 based on a name length >15 check.
Adding 2-3 checks with 2-3 different font sizes would make intermediately long names look better, and support extremely long names like Vlad.

This is a bug because the arrow to go to the user details page is not accessible

Especially needed for names

Write tests for core features of app

Bonus: setup CI to run on every PR

Images are lost when app is restarted.

We should cache profile photos from directory and post preview images (which tend to be large size)

Whenever I click on a phone number to dial them, from the app.... the number in my caller app is shown as ++91.. instead of +91.
It might be a local glitch.

![Uploading Screenshot_2020-09-29-19-42-50-914_com.android.contacts.jpg…]

Leading to ERR_CLEARTEXT_NOT_PERMITTED in Android webview.

HTTPS links are working.

Add a floating action button in directory. When clicked, it takes you to the search bar.

When user scrolls down, the FAB is hidden and vice versa

Searching will be done on client side.

If we reuse the same search bar in directory, we have to decide if we're calling /users?search= API or doing everything locally

TODO: Also add a getting started document with all the places where people have to "YOU API KEY HERE" so they can get up and running with the app asap

We can then read this file in AndroidManifest.xml and the iOS Swift files

Point to MF main website's donate link

Improve support for supported social media profile links.

Allow ID for instagram instead of full URL?
(Not possible for LinkedIn)

Pre-fill "https://instagram.com/" on press of text field, if previous data is empty?

Don't show error for "https://www.instagram.com/..."

Don't wait till "://" to remove error for https/http links. Might confuse users while adding https links.

This is basically to separate the error message/UI validation layer from the API validation layer in a better way so it's less confusing to users.

This is a bug in the Google maps plugin. The workaround is to increase iOS version to 9 (from 8)

Launching a wa.me//[country_code+phone number] with a whatsapp icon button in the "social media line item" might be useful.

Note: this assumes that the user enters a Whatsapp phone number. We could also add a notice in the profile edit phone number field that this would also reflect as a whatsapp number.

Saving a number as WhatsApp or not and then deciding whether to show only the phone number or show both the phone number and a WhatsApp icon button would need backend changes