Chapter 3:
Chapter 3 introduces ArcGIS Experience Builder, which is a more flexible tool for creating web applications. To be more specific, it allows users to design apps with customizable layouts and to integrate multiple types of content (like maps, charts, and text) into the app. Users can control how the app looks and behaves across different devices. This makes it possible to create interactive experiences tailored to specific audiences or purposes, depending on what data you are displaying. What stood out to me is how customizable it is compared to other tools. You can organize an entire interface of info relating to your map, instead of simply creating the map. You can choose from different pre-made templates and widgets, allowing for room for creativity when deciding the best way to display your information. I also thought it was interesting that there are both layout widgets (that organize content) and functional widgets (that perform tasks). As previously mentioned, the app can be displayed across different devices, including mobile phones. This makes the apps being created much more accessible and versatile. As someone who has experience with graphic design, I appreciated how Experience Builder encourages well thought out design. Sometimes, when scientific data is displayed, it can come off as boring to the average person due to the lack of visual flair. ArcGIS Experience Builder negates this by allowing freedom for design. It’s more than just showing data; it’s guiding users through a visual experience so they can explore the information effectively.
Chapter 4:
Chapter 4 introduces ArcGIS Web AppBuilder and expands on the idea of mobile GIS. In particular, Chapter 4 highlights the advantages that mobile GIS provides. This being an avenue to easy data collection, real-time updates, and the ability to access these GIS tools/data from virtually anywhere. Everything previously mentioned makes it much simpler for users to gather and update data directly in the field without needing to return to a desktop computer. Web AppBuilder is another tool for creating web GIS applications that happens to be effective when used on mobile devices. It is more template-based, meaning it is quicker and easier to build these applications. However, it offers less customization and fewer options for organizing compared to Experience Builder. This tradeoff is important depending on what the app you’re creating is trying to achieve. For example, the simplicity of Web AppBuilder may make it easier for the general public to use, or just easier to access in general. As well as a quicker application production time when time and resources are limited in specific cases. Despite the simplicity of Web AppBuilder when compared to Experience Builder, it still provides a variety of built-in widgets. These include search tools, measurement tools, and filters. All of which allow users to interact with the map/data without needing an extensive knowledge of GIS programming or cartography. Overall, both chapter tutorials were understandable and simplistic to perform.
Applications:
I could create an interactive web application involving water quality. I am very interested in hydrology, and the concepts discussed in these two chapters could aid in displaying/gathering data related to hydrology and water quality. Let’s say I find and use data from local streams and ponds collected by scientists. I could design an app to show maps of sampling locations, and input filters that let users focus on specific bodies of water. First, I would need to decide if I want to use Experience Builder or Web AppBuilder. Experience Builder could allow me to design a highly detailed and fully customized interface, effective for scientists and other academics to study water quality patterns. On the flipside, Web AppBuilder would allow me to design a simpler, more user friendly version of the previous app that could be easily accessed and understood by the general public.