Great to see initiatives like this. However, everyone who can should be using a teledoc and getting instructions before visiting a testing site. Otherwise you're putting healthcare providers and patients in danger (a former colleague drove to multiple stations to try to get tested and he interacted with a bunch of HCPs).
Do you mind making it clear in the tool that someone viewing the site should first contact a teledoc?
But shouldn't an effort be made to make things easier and safer? Imagine a drive-through location with the web address of an intake app over entrance. You do intake with the app in the parking lot and then get cleared to go through. Everything automate and nearly free of human contact.
Apparently not, unfortunately. Each person who gets tested uses up masks, gloves, and other protection equipment that is in short supply. If you think you might have the virus, quarantine yourself or go to a hospital if you need emergency care. Getting tested if you’re healthy won’t change the outcome.
Many jurisdictions (including mine in Calgary) are telling people NOT to visit hospitals. We’re supposed to do the health authority’s online self-assessment and call our local healthcare number to get instructions.
Sure, we have a shortage. But mask and other equipment production is going to be ramped up shortly. Testing and is going to be the second part of any virus suppression effort.
And yeah, currently, we got nothing. Everyone quarantine, the sick-enough go to the soon-to-be overwhelmed hospitals. But we have to look plausible measures once we have resources, right?
You overestimate how tech savvy the common population is and how much hand holding is actually required to achieve this drive through testing efficiency.
People would get in line with their car to ask the attendant questions or for IT app support. There are language, accessibility/disability, cultural, etc. barriers (to name a few).
-Healthcare (shelter in place info, testing like Verily Baseline, etc)
This info is currently scattered across the Internet and we're aggregating it in one place. It's hosted on Github using markdown so anyone with spare time can be a massive help (https://github.com/coronawhatnow/coronawhatnow.com).
I wrote an automated tool to check TP inventory on Walmart.com and alert when inventory become available, I've been thinking on building an app for that but would need some help.
I see the language description on the site now but it was hard to spot until I looked really carefully. That said, I don't see a way to use this as a web app, only to download it for a mobile device. I know the phone number is for getting a download link but the thing is I do not want to download it.
Flowlingo dev here. Thanks for the feedback! It's been a while since I've taken French, but one thing we plan on adding is translations of individual words in-context. For example, in Spanish, if you tapped an individual verb, the translation would be properly conjugated in relation to the sentence. We'd love to hear your other feedback, feel free to chat with us in the app (tap "Help" and scroll to the bottom), or email us at support@getflowlingo.com.
I think both could be useful. If I'm reading something in russian, for example, иду, that on its own isn't very interesting to me, I want to be able to see the whole verb, especially when there are stem changes etc.
I think you would find it difficult to conjugate _the translation_ as the conjugation tables/rules differ between the languages and the mapping is not one of one. For example, English only has 'you' but French has both singular and plural forms. Russian has the declension as well (Именительный, Родительный...)
I think it would make more sense to normalize at the _source_ language as I wrote originally. See also the other comments in the same sub-thread.
As to the other ideas, like I said "10 pages". And a lot of them about the system that really accumulates the knowledge about you to give you the best training. See, for example, https://solaresearch.org/ for academic foundation of that and https://french.kwiziq.com/.
But here is a couple of other thoughts. Feel free to contact me if they spark anything:
* Synchronized text and audio (e.g. Amazon Whispersync). Has been done by many people but was usually done by hand (was too expensive) or by text-to-speech on the fly (which was awful at the time); yet it was always welcomed. TTS is now much better, but also maybe some work can be pre-calculated (rather than immediate).
* Use the Google API mentioned before (syntax tree) to extract sub-sequences (named entities, stable expressions, etc) and present those instead of individual words; this helps to see them over and over within different sentences. Even showing a verb and its dependencies is useful. This also allows to include grammar references for tenses/irregular verbs/expressions, etc.
* Dictionary entries by the normalized form (lemma) of the verb, noun. Flashcards that first show the multiple contexts line of the same verb in the same form, then same verb in other forms and only then translation.
* Color code the text being read by word type. So all verbs as red, all nouns as blue, all adjectives as green, etc. Also see https://langliter.com/, they do (and lemmas) that as "highlights".
* Color code the text by words known. Green as those learned already in that exact form. Yellow as those learned in different form (different tense, different conjugation, etc). Red as those unknown.
* Pre-flash. Analyze text (small chunk), compare again flashcards and compile the list of words/expressions and let person practice them first. Then read the actual text with the hope to increase the speed of comprehension.
* Slightly further along are things like "Words of the day" emails that analyze your flashcards to give you more words in the same category (arm+leg=>offer head). Or touch typing game using your own flashcard words. Or conjugation table training using collected context.
These two forms are a dialect (variation?) of English, mostly used in Southern USA.
Also, if I remember my John McWhorter correctly:
1) "y'all" refers to a group majority (e.g. a group of 10 people within the global collective of 20)
2) "all y'all" refers to the complete set (all 20)
Both of these are contextually narrow than "you" which can refer to a single person or to an undefined sized group.
A possibly better example would have actually been "thou", an archaic singular 2nd person pronoun.
However, all of this is just further proof that the equivalence in conjugation is a harder problem that could be imagined. So, thank you for contributing a good example.
In short, we're working hard and making strides, but we have a lot of work to do. We love hearing feedback—keep giving it to us. It keeps us hungry to make things better.
Let me start by giving some kudos. I had a chance to use a GUI tool that lets a developer test FB API calls. I'm not sure if this is officially released yet but it was a fantastic tool and a step in the right direction! (fyi: I got the link from a presenter at a hackathon ... forget the details).
Like some of the other folks here, I have burned many many hours trying to get the FB API to behave nicely. I think the core issue is documentation coupled with the velocity with which things change. I understand that the mantra for the company is "Move fast, break stuff" but I don't think it is right for you to cause developers pain. While you folks might have a lot of dev resources, not everyone does. A lot of times, I can see the API changes being done for good ... i.e. rename paramters or move'em around. The problem is that if you don't flag the change and/or documented this, you've pretty much guaranteed developer pain.
I understand when you move fast, you don't have time to document. People naturally turn to blog posts. This adds to the pain because half the stuff works while the other doesn't. My experience using the API at a recent hackathon was piece together fragments from different blogs and hope for the best.
So if there is one line of feedback you take from this .... if you change your API, think about it from the external developers standpoint.
More documentation, up to date and better organized. I know you have made strides, but please don't slack.
You should be sending all developers weekly email blasts about upcoming changes, recent changes and known bugs.
I'm pretty sure my company would pay for some sort of VIP tech support, even if it was just someone we could ping who would simply respond with "oh, that feature was switched off last week".
Do you mind making it clear in the tool that someone viewing the site should first contact a teledoc?