This app displays different agritourism attractions in the state of Washington.
Agritourism is a fast-growing industry. This is a handy app that a state or region can provide to visitors in order to promote tourism in the area: it features wineries, farms, restaurants, and more. Users can view attractions by category, use the map to locate each venue, and contact the tourism board to give comments and upload photos of their experience.
Also see: tablet mode & fullscreen mode
This is a high-level model of both the data entities and the UI elements in the app.
This is a preview of the data sets used in the app.
How we built this app
This app displays attractions and their associated images, as well as their locations via a Map view. It takes advantage of the following features: [Refs] The app has three tables: Attractions, Visitors, and Categories. We want to group by category in the "All" UX view, but we also want to be able to display images when the user clicks on the category. To do this, we need to use a Ref from the Category column in the Attractions table to the Categories table. [UX View as Ref] We wanted to see the categories as a gallery in the 'All' UX view, so we set the 'All' UX view as a 'Gallery' View Type. But when we click into a category, we need to be able to see its corresponding images. In order to accomplish this, the 'All' UX view needs to point to the Categories table. Then we created a UX view of the 'Deck' View Type that points to the Attractions table. This ensures the refs to that table will display the corresponding images. However we do not want that UX view to show in the app-- so we named it 'Attractions Inline' and indicated 'Ref' as the Position. View Types in the 'Ref' position do not show in the app and only act as indicators of what kind of View Type to render for the items in the Ref column. When clicking into a category, we wanted to utilize a slideshow view so both the category and its associated items would show in the view. In order to do this, we created a UX View called "Category Detail" and marked the Position as "Ref"-- this way the view wouldn't show up in the app but would render the categories as a slideshow. [Round Deck View Images] We indicated 'Round Image' as the ImageShape for the Ref Deck View. [Security Filters] The 'Contact us' view is based on the 'Visitors' table (that lives within the master Washington Agritourism spreadsheet). We want users to be able to fill in their information in the 'Contact us' form, but we don't want them to be able to view past responses. In order to accomplish this, we set a security filter on the Contact us table from the Advanced Editor>Behavior>Security tab, indicating 'False' as the filter.