Evaluate Crowdsourcing and Archiving on mobile

[dennyabrain]

Overview

Create a flutter app that allows tattle to crowdsource slur words and website URLs.

This issue is a continuation of our exploration with #255

Unlike #255, where the exploration was to remove slurs from a feed on user's phone, the scope of this issue is only to evaluate what all is possible on mobile wrt crowdsourcing slurs and website URLs via the "Share" feature on smartphones. Atleast on Android I know that one can select a word and click "share" to forward that word to another app. And the same is possible for URLs and content on social media apps. So using these features, it should be possible to forward the slur words and various types of URLs (web url and app content URLs) to the Uli app.

The unknowns to resolve are :

1. Does the same sharing mechanism work on ios and android
2. The quality of third party libraries that exist for implementing the share feature on flutter

Out of scope

1. Once the app receives it, we can easily forward this to the Uli server. We don't have to do that as part of this issue. Being able to show the shared data in the app is acceptable for this proof of concept.

[dennyabrain]

Now that we have a google workspace account, we could use google's appsheet platform. Which is low/no-code platform to build apps backed by google products like google sheets, form etc.

Sharing some notes from initial exploration :
pros :
when i released the app and shared it with my gmail account, i got an email saying "Install App", when i clicked on it, it went to my Android App store to install "Google Appsheet" and then after installation it automatically opened the custom app that I had created.
I feel like the onboarding flow is super smooth, you get an email invite, you go to your app store (which hopefully you are familiar with) and then you can start using a custom app.
To be checked : what is the flow like for apple users. does appsheet have an ios app too?

cons :
the only way to login is using a gmail account! so this explains how they easily do access control and login but it restricts people from using non gmail accounts. not sure if this is a deal breaker for our annotators but something to keep in mind. The good thing is that every contribution is tied to an account, enabling quantification of individual contributions etc.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.