Here is a question about the setting of keywords for an app on the appStore.
Let me take an example. Let us say my app is called Shakespeare and it is an English learning app.
The first two keywords coming to my mind are: English and Learning.
Obviously only with those two keywords, there are already a number of ways a user might perform a search.
Giving only a few examples here:
Search for: “English Learning”.
Search for: “Learning English”.
Search for: “english learning”.
Search for: “english”.
Search for: “english study”.
And I could easily make the list much longer.
My question is (only sticking with my two keywords) what is the best way to put them when filling the form for the submission to the appStore?
“English,Learning”
“English,Learning, English Learning, Learning English”
??
If 1) is OK to match all cases obviously that is better. Do the cases matter?
Case 1 matches all cases.I tested that right now.
Related
As stated in the question : I am developing an app for French kids to learn English vocabulary. I have added a SpeechToText functionality using the SpeechToText package, which really works well.
However, I am hitting a hard rock now... One of the activities proposed to the students is simply "Listen and repeat", so that they progressively improve their pronunciation.
I thought of using the SpeechToText package as well for this... and it would work if the students pronounced the words quite well.... One example : The sound "TH" for a French speaker is problematic and is very often pronounced as a "Z"... so the app never really recognize a word like "Father"... it keeps thinking the user says "Fazza".
Is there a way to compare the "good pronunciation" of a word to what the user says... get a percentage of "similitude". I know we can compare strings that way.
Would anyone know of a solution for this issue ? Any advice ?
You can use the speechace APIs to get the following features:
Pronunciation Assessment
Fluency Assessment
Spontaneous speech assessment
this may be a noob question - but I hope to get an answer from an experienced person,
because we have to switch our settings and would like to do it correctly the first time.
At the moment the default language is set to German. English is defined as another language.
When somebody from France looks at the website, it is shown in German first, he then has to switch to english manually. For an english visitor everything is fine.
So what should we do:
1) Set the default language to english and have german as second language? What about guys from Switzerland, Luxemburg, Liechtenstein and Austria then. Do these have to be defined seperately as they are also seperately selectable as windows languages?
2) Is there an option to simply say: Every visitor that is not german speaking should get the english website in default? And even in this case, will this then recognize the different german options explained in 1?
Sorry if these questions are stupid. ;-)
Thank you,
Fabian
Your aim is to change how visitors see the website, but your are asking how to change the editing of the website accordingly. Luckily it is a CMS and you can separate those concerns.
What you seem to look after is a component that analyses the IP/language/browser properties of the visitor at first page load and that there are rules what to show (e.g. show English version except your mentioned countries). There are extensions for that specific purpose like https://extensions.typo3.org/extension/locate or others: https://extensions.typo3.org/?L=0&id=1&tx_solr%5Bq%5D=language
That way you don't need to change the default at all.
I am using the Actions on Google Trivia Game template.
Special characters () are not displaying in the chat window.
In google sheets, I have given in the following format.
Question: How to Add an item to the end of the list
Answer1: append()
Answer2: extend()
In google assistant, it was displaying without parenthesis. How to give questions and answers with parenthesis and other special characters?
This is a good one - it looks like the processor that uses what you entered removes special characters. This does seem odd when you look at the question and the suggestion chips.
However... it makes sense if you think about how people are expected to answer the question. If you run it in "speaker" mode, it won't display the suggestion chips, but users will be expected to verbally give an answer. It is pretty difficult to give an answer with parentheses - so the system automatically removes those from what is expected.
I asked about converting speech to text in c++ but my question seemed to be unclear and also the answer I got. I have already heard that we should have "speech" in a wave file. so what to do after that? I said I want to do it on my own, I mean without using windows's facilities and API.c++ libraries are allowed if there are. I need to know how it works, is it impossible?? that it will take a million years. there is no tutorial thing in Google about it. at least tell me some steps to light my path.what are the titles of things I have to do or learn? there are so many thing that are using converting speech to text, like i can say john to my mobile phone and it calls john. does not it recognize john? it seems to be a little bit easy so it is possible to learn not 'a million years'. I need to learn how to convert just some short sentences to string. for now the qualities like pronunciation is not important . what are the bases and where I can learn about them? look , i need to say one sentence to computer and then computer has to choose one the answers that I have already recorded, so I need to convert to string to compare that string with the recorded string sentences. please some one tell me what to do or what to search or where to look or where to go or who to see?
Does anyone have any idea what boolean logic is acceptable on the facebook graph api? They have the worst documentation, forums, assistance known to the developer world. I tried using OR and it does not seem to be working. AND seems to be implied with spaces or commas.I am trying to search for multiple terms or using OR and NOT.
You can do AND and OR, when searching for posts, like:
http://graph.facebook.com/search?q=watermelon%20|%20banana&type=post
The AND operator you can use with space or +:
http://graph.facebook.com/search?q=watermelon%20banana&type=post
You can search for terms like "bruce lee" too, using "":
search?q="bruce lee"&type=post
Resuming: " | " = OR
" " and "+" = AND
I did not find a way to use the NOT operator
And I agree, it is the worst API documentation ever.
It seems, | is not working any more, I've just discovered it today. Only posts matching ALL words from query are found.
Only to share:
'POST' search will no longer be possible from April 30th 2015. See https://developers.facebook.com/docs/apps/upgrading#upgrading_v2_0_graph_api under the paragraph "Removed endpoints":
Public post search is no longer available.
(/search?type=post&q=foobar)
Right now if you enter a number of words in the search term, separated by space - then you should get back relevant entities that have those words (anywhere in the entity, in any order). "bruce lee" --> "Bruce is a nice guy, he likes Lee" would be a possible result.
There is no "or" operator that works.
I opened a case at Facebook, which was closed hours later for the reason it "works as specified" here: https://developers.facebook.com/x/bugs/138296099674000/
This is a bug tracking tool, but the details you added here don't
represent a bug report - it appears to be you asking for assistance on
how to make certain things work in the search API or a feature request
for the search API to start supporting different operators - only the
behaviours documented here are
supported:https://developers.facebook.com/docs/reference/api/search/
Obviously I can't disagree with the correctness of this claim (especially given #tesserex and #vbNewbie 's observations above) BUT let's not give up.
Since I think we all agree the current functionality is limited / limiting, I would like to encourage all of the people that agree with me to open bug reports and / or feature requests (how do you open a feature req. for FB?) so that this will get prioritized correctly.
I don't think the current functionality does Facebook or the developers any good, and I don't think it should be a major effort for FB to improve it significantly.
So let's gently apply some pressure ;-)
It's not working like that anymore, but I'm finding that this will work now (for search for watermelon OR banana: http://graph.facebook.com/search?q=watermelon&q=banana&type=post