In this multizap on every new entry for theTypeform (step 1) we lookup the unique id of the adventure in the adventure table (step 2). In our app, the url for the Typeform to collect the rating (here the hidden field is called adventureid and the id itself is generated in Airtable from the adventure name): you can use it to display the respondents name in a question. This hidden field data is then available for logic or personalizing the Typeform, i.e. There is a really useful feature in Typeform called hidden fields (you can learn more about them here) which lets you personalize a Typeform by including it in a URL parameter when you do the initial call to the Typeform. To make a better user experience, I had to ensure the rating for an adventure was stored for the right one without asking the user each time. Now I am a little biased, but there are not much better tools for collecting data than Typeform (especially as it was Nicolas who made the suggestion), so we added a simple rating question as a webview. Although Bravo Studio does allow direct users input at the time of writing we don’t have beautiful rating input field, so we thought for this exercise we could use a 3rd party tool to collect this information. Now the adventure app already does step (1), so the first issue was how to collect the users rating. Compute the average of all the ratings of an adventure and add that to the adventure information which can be displayed as a list.In the detail on an adventure allow input on rating the adventure.Display the list of adventures from Airtable.But the challenge here was that we had to also record the user rating and provide an average. Now our adventure app (one of our example apps in the resources page here) is easy to connect to its data in Airtable (its one of the best online data stores with great API support). ![]() Our example adventure listing app In the Air(table) tonight
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |