Continuing my research on the topic of “Slowness”from last semester, I will be doing further work on this topic as part of the Design & Research II course with Birgit Bachler PhD.
For the final assignment, I will need to record a 2-minute video of the final prototype — in my case, I plan to use prototyping in Figma, which each of you will be able to test. The research will again focus more on contextual analysis, as well as user testing, bibliography, and heuristic evaluation.
Final Video!
Continuing my research on the topic of “Slowness”from last semester, I will be doing further work on this topic as part of the Design & Research II course with Birgit Bachler PhD.
For the final assignment, I will need to record a 2-minute video of the final prototype — in my case, I plan to use prototyping in Figma, which each of you will be able to test. The research will again focus more on contextual analysis, as well as user testing, bibliography, and heuristic evaluation.
Comparing default routes and experience-based routes 🛣️
For this post, I decided to conduct a small practical experiment and compare a standard navigation route with one that more closely resembles the concept behind my future app. I chose the same route: from my current location to Hauptplatz in Graz. It was important to me to look not only at the time and distance, but also at how the walking experience itself changes.
On Google Maps [1], the standard route looks very straightforward and functional. The app suggests the fastest option: 35 minutes, 2.6 km, mostly along Annenstraße. This is convenient if the goal is simply to get to your destination. But with this option, the walk feels more like a task: follow the line, don’t get distracted, and reach your destination.
Then I manually created a second route in Google Maps and added stops: BILLA PLUS, Volksgarten, and Gelateria Italiana by Luis, and only then—Hauptplatz. The time increased to 42 minutes, but the route itself became completely different. It’s no longer just a path from point A to point B, but a little walking itinerary: pop into a store, walk through the park, buy some ice cream, and only then head to the center.
I also ran the comparison on Mapy.cz [2]. The direct route is shown there as 43 minutes, 2.6 km, while the route with additional stops is about 50 minutes, 3 km. What I especially liked about Mapy.cz is that the urban environment itself is much easier to make out. You can see parks, green spaces, paths, the terrain, the river, and the neighborhood’s layout. The map looks more detailed and “outdoor-oriented.” Visually, it’s not as minimalist as Google Maps, but for my purposes, that’s actually a plus because it helps me not just walk, but understand the space around me.
This experiment helped me better understand the concept behind my app. I don’t just want to make routes longer. The idea is for users to be able to choose not only their destination but also the type of route: fast, leisurely, green, adventurous, social, or with short stops.
In the next prototype, I want to develop this logic further. For example, if a user selects a “slow route,” the app could automatically suggest a path through a park, a quiet street, a café, or a spot for a short stop. In other words, the map becomes not just a navigation tool, but also a tool for planning a walk.
This test showed me one simple thing: navigation doesn’t have to be just about the shortest route. Sometimes an extra 5–10 minutes can make a route much more enjoyable, personal, and memorable.
Sources 🛈
[1] Google Maps. Google LLC. Available at: https://www.google.com/maps
[2] Mapy.cz. Seznam.cz, a.s. Available at: https://mapy.cz
Continuing my research on the topic of “Slowness”from last semester, I will be doing further work on this topic as part of the Design & Research II course with Birgit Bachler PhD.
For the final assignment, I will need to record a 2-minute video of the final prototype — in my case, I plan to use prototyping in Figma, which each of you will be able to test. The research will again focus more on contextual analysis, as well as user testing, bibliography, and heuristic evaluation.
Social geography and who the city is for 🤼🏻
The next important question for my project is: who is “slow navigation” actually designed for? At first glance, it might seem that “slow routes” are suitable for everyone: tourists, locals, people who love to walk, or those who want to explore the city. But if we look deeper, the city isn’t the same for everyone. Different people move through it in different ways, and this falls under the umbrella of social geography.
Social geography helps us think of the city not only as a physical space but also as a social experience. The same route can be pleasant for one person and inconvenient or even unsafe for another. For example, a tourist might be looking for beautiful streets and cafes, a local resident might be looking for a peaceful route after work, someone walking a dog might be looking for green spaces, and a person with limited mobility might be looking for a flat route without steep inclines or stairs.
Social geography is a subfield of human geography that examines the relationship between society and space. While there is no universally accepted definition, it is generally understood as the study of societal dynamics from a spatial perspective, exploring how people interact with their environment across time and place. This area of study encompasses various topics, including the differences between locations and their residents, the transformations of places, and the ways individuals perceive and alter landscapes. [1]
The PDF [2] includes an important note that Situationism and similar theories often stemmed from a Western, male, and academic tradition and may not have taken into account the experiences of women, queer people, colonized populations, and people of color. It also states that it is important to consider structural barriers and the fact that not everyone can “wander” through the city with the same degree of freedom.
This is a very important point for my app. If I use the ideas of dérive and free exploration of the city, I can’t simply say, “Let people go wherever they want.” For some, this truly represents freedom, while for others, it means stress, risk, or physical limitations. Therefore, slow navigation must take into account not only mood and interests, but also safety, accessibility, physical exertion, lighting, proximity to public transportation, and the user’s personal boundaries.
Here, I also find the idea from data feminism useful. Authors Catherine D’Ignazio and Lauren Klein [3] suggest thinking about data through the lens of power, context, and inequality. For my project, this means that a map shouldn’t pretend to be neutral. If an app shows the “best route,” we need to ask: best for whom? For a young tourist? For an older person? For someone with anxiety? For someone who doesn’t speak the language? For a young woman walking alone at night?
That’s why, in the future prototype, I want to focus more on modes and settings – not just “fast/slow,” but more specifically: quiet, safe, green, accessible, dog-friendly, low-stairs, familiar, and exploratory. This makes the app not just a pretty alternative to Google Maps[4], but a more human-centered system that acknowledges the different ways of experiencing the city.
For me, the main takeaway from this phase is this: slow navigation shouldn’t romanticize walking. It should take into account that a city can be inspiring, but also challenging, noisy, inaccessible, or unsafe. If the app wants to create higher-quality routes, it must consider not only the beauty of the path but also the user’s social context.
Sources 🛈
[1] EBSCO Research Starters. Social Geography. EBSCO Information Services. Available at: https://www.ebsco.com/research-starters/geography-and-cartography/social-geography
[2] Bachler, B. Intro to Information Design – Session 5: Commuting Cartographies. FH JOANNEUM, 2025.
[3] D’Ignazio, C., & Klein, L. Data Feminism. MIT Press, 2020. Available at: https://data-feminism.mitpress.mit.edu
[4] Google Maps. Google LLC. Available at: https://www.google.com/maps
Continuing my research on the topic of “Slowness”from last semester, I will be doing further work on this topic as part of the Design & Research II course with Birgit Bachler PhD.
For the final assignment, I will need to record a 2-minute video of the final prototype — in my case, I plan to use prototyping in Figma, which each of you will be able to test. The research will again focus more on contextual analysis, as well as user testing, bibliography, and heuristic evaluation.
Psychogeography and Dérive 🧠
One of the ideas that fits my project particularly well is psychogeography. Simply put, psychogeography explores how a city influences our emotions, moods, and behavior. It’s not just about streets and buildings, but about how we experience space as we move through it. In the PDF [1], this topic is introduced through Guy Debord and his work “The Naked City“[2]. It is described as a psychogeographic map that reveals not a conventional map of Paris, but the hidden psychological and emotional connections between urban fragments.
This is a very important shift for my project. Conventional navigation revolves around point A and point B. The user enters an address, the app calculates the route, and that’s it. But psychogeography offers a different way of looking at the city: not as a problem to be solved, but as an environment to be explored.
This is closer to my question: can navigation be not only efficient, but also more mindful, personal, and slow?
This is related to the concept of dérive, or drift [3]. In the presentation, dérive is explained as a method of exploring the city through unplanned, almost aimless wandering. A person does not follow a strictly predetermined route, but instead allows themselves to respond to the atmosphere of the place, random turns, their mood, and unexpected encounters. Debord described dérive as a practice distinct from an ordinary walk because it involves paying attention to the city’s psychogeographical effects and atmospheres.
I don’t want to literally turn the app into a chaotic, aimless wander. But I’m interested in adopting the very principle of dérive: a route can be not only functional but also open-ended. For example, the app could offer not just one “correct” path, but several options: a calm route, a curious route, a green route, or a social route. The user is still moving toward a destination, but the path becomes more flexible and dynamic.
It also helps me take a critical look at modern maps. Many apps try to eliminate uncertainty: turn right, walk 200 meters, and you’ll arrive in 6 minutes. On the one hand, this is convenient. On the other hand, people stop noticing the city around them. They look at the screen instead of their surroundings. In my project, I want to try to bring some of that attention back to the user.
For the prototype, this could take the form of a specific feature. For example, “Explore Mode” might occasionally suggest a slight detour from the route: walking through a park, taking a quieter street, choosing a route with interesting architecture, or making a short stop. It’s important that this isn’t forced, but feels like an invitation.
In this way, psychogeography and dérive help me formulate the foundation of the project: slow navigation isn’t just about “walking longer.” It’s a way to design a route so that a person not only reaches their destination, but also feels, notices, and remembers something along the way.
Sources 🛈
[1] Bachler, B. Intro to Information Design – Session 5: Commuting Cartographies. FH JOANNEUM, 2025.
[2] Debord, G. The Naked City. Psychogeographic Map of Paris, 1957. Available at: https://www.researchgate.net/figure/Guy-Debord-The-Naked-City-A-Psychogeographical-Guide-to-Paris-1955_fig2_370004669
[3] Debord, G. Theory of the Dérive. Internationale Situationniste, no. 2, 1958. Available at: https://rohandrape.net/ut/rttcc-text/Debord2006e.pdf
Continuing my research on the topic of “Slowness”from last semester, I will be doing further work on this topic as part of the Design & Research II course with Birgit Bachler PhD.
For the final assignment, I will need to record a 2-minute video of the final prototype — in my case, I plan to use prototyping in Figma, which each of you will be able to test. The research will again focus more on contextual analysis, as well as user testing, bibliography, and heuristic evaluation.
Information design, maps and my app 🗺️
In this post, I want to connect my project to the topic of information design and to material from the “Commuting Cartographies” class. I found this PDF [1] very useful because it shows maps not just as a tool for finding your way, but as a way to understand, interpret, and even change our perception of the city. In the presentation, a map is defined as “a spatial representation of reality.” But another idea is particularly important for my project: maps don’t just show the world- they shape it.
This is directly related to my idea for a “slow navigation app.” Usually, a map is perceived as a neutral tool: it shows where we are, where to go, and which route is the fastest. But in reality, a map always chooses what to show and what to hide. For example, a standard 2D map shows streets, buildings, and names. A 3D map adds a sense of scale and space. A bird’s-eye view helps you get a better visual feel for the city. Psychogeographic maps, on the other hand, may not show roads at all, but rather emotions, smells, sounds, or personal impressions of a place. This is clearly illustrated in the PDF using examples of different map types: top-down view, bird’s-eye view, 2D map, and 3D/extruded map.
For my app, this means I don’t have to design the map exactly like Google Maps [3]. I can think of the map as a system of layers. For example, one layer could show the most peaceful route, another could show green spaces, a third could show places to stop, and a fourth could show the emotional or sensory characteristics of the route. This helps shift the focus from “getting there faster” to “experiencing the journey better.”
I also liked the CityMaps [4] example, where logos and place names are used instead of satellite images and building outlines. This shows that a map can be not only geographical but also social: people often navigate not by coordinates, but by cafes, stores, familiar landmarks, parks, or visual cues. This is important for my app because slow navigation should be closer to how people actually experience the city.
Another useful takeaway from the PDF is the importance of visual hierarchy. If everything on a map is equally important, it’s hard for a person to know where to look. In my interface, this means I need to carefully manage text, icons, colors, and layers of information. If I want to create a calm app, it shouldn’t overwhelm the user. On the contrary, it should gently guide their attention.
Thus, this material helped me realize that my project isn’t just a “map with pretty routes.” It’s an attempt to design a different kind of information system for the city. The map in my app should not only guide people but also help them notice, choose, stop, and build a more personal connection with the space.
Sources 🛈
[1] Bachler, B. Intro to Information Design – Session 5: Commuting Cartographies. FH JOANNEUM, 2025.
[2] Wood, D. Rethinking the Power of Maps. Guilford Press, 2010.
[3] Google Maps. Google LLC. Available at: https://www.google.com/maps
[4] Citymaps. Available at: https://citymaps.com
Link: DesignResearch.mp4
Looking back at this semester, I think the biggest challenge for me was figuring out what I actually wanted to focus on for my master’s thesis. At the beginning, I only knew that I wanted to work with older adults and that I was interested in topics like digital literacy, education and tangible interaction. It took a lot of reading, observing and prototyping before these pieces slowly started to come together.
Even though I only really found my direction during the last couple of weeks, I don’t see that as wasted time anymore. Exploring different ideas helped me understand what actually interests me and, just as importantly, what doesn’t.
One thing I definitely discovered this semester is how much I enjoy working with tangible interfaces. Designing something physical that interacts with the digital side feels like a really exciting topic to explore, especially in the context of accessibility and older adults. At the same time, I still enjoy the technical side of interaction design and would love to combine both in my master’s thesis.
The NFC book is only an early prototype, but I think it has shown me a direction that I want to continue exploring. Over the next semester, I would like to test this concept with older adults.
Since I came up with the idea of creating a physical phone book in my last blog post, I decided to ask ten older adults, all around the age of 65, what they actually like to use their phones for. This time, the conversations went much better than my previous ones. Everyone was able to tell me quite clearly what they regularly use their phones for.
What I found even more interesting was that many participants started talking about their frustrations with smartphones on their own. While answering questions about their everyday phone use, they often mentioned situations where they felt confused.
For this very short interview, which was more of a questionnaire, I simply asked participants what they use their phones for most often. The most common answers were: making phone calls and using WhatsApp, either for texting or sending voice messages. Other frequently mentioned activities included looking at photos, checking the weather and reading the news. Some participants also said that they regularly listen to music, radio stations or playlists using apps on their phones.
These results were somewhat interesting for me because they support my idea that older adults often use a relatively small set of functions very frequently. This made me think that focusing on simplifying these tasks, rather than trying to simplify the entire smartphone experience, could be a direction for my research.
| Activity | Participants (n = 10) | Percentage |
|---|---|---|
| Calling (normal) | 10 | 100% |
| Watching Photos and Videos | 10 | 100% |
| Taking Photos | 10 | 100% |
| Calling (video) | 8 | 80% |
| Sending Messages (WhatsApp) | 7 | 70% |
| Listening to Music | 6 | 60% |
| Checking the Weather | 5 | 50% |
| Reading News | 4 | 40% |
| Listening to Radio | 3 | 30% |
Since many of the people I interviewed mentioned that they mainly use their phones to stay in touch with family and friends, it became clear that social connection plays a very important role for them.
Access to digital technology plays an important role in the lives of many older adults, as it can significantly influence their quality of life, social participation and ability to manage their health and well-being. Social isolation is a significant concern for the elderly population which is often caused by shrinking social circles either because of retirement, illness or death. [1]
As a result, maintaining social connections becomes increasingly important in older age. One of the most important benefits of digital technologies is that they can help reduce social isolation and loneliness. Through video calls and social media, older adults can stay connected with family and friends and continue to participate in social life. [1] Regular social interaction through digital technologies is also associated with better subjective health and overall well-being. [2]
Beyond supporting social connections, digital technologies can also help older adults maintain their independence and quality of life. They can support everyday tasks, promote cognitive engagement and enable older adults to remain active and participate in society longer. [3]
These findings are also in line with the interview results, where participants mentioned that they mainly use technologies such as smartphones to stay in contact with family and friends.
After trying out different ideas, I ended up focusing on the NFC phone book. The idea came from my observations and the short interviews I did. Most of them told me that they only use a handful of functions on their phones regularly, mainly calling family and friends, looking at photos, listening to music or checking the weather. That made me think: instead of trying to simplify the whole smartphone, why not just make these everyday tasks easier to access?
The book is divided into different sections based on most used functionalities, like calling family, listening to music or viewing photos. Every page contains pictures or symbols with NFC tags hidden inside. To perform an action, users simply open the page they need and hold their phone over the corresponding picture. For example, holding the phone over a picture of their daughter would automatically start a phone call.
I decided to go with a book because it feels familiar. Earlier, I experimented with individual NFC objects, but I realized that they could easily get lost and would need to be stored somewhere. A book keeps everything in one place and also gives clear instructions.
At this stage, the prototype is mainly meant to explore whether a familiar object like a phone book can make smartphone interactions feel simpler. Instead of navigating through apps and menus, users interact with pictures and pages, which hopefully reduces some of the barriers that older adults experience when using smartphones.
I already tested it with my grandmother. Her comment: “It feels like magic!”
[1] P. Bhowmick and E. Stolterman Bergqvist, ‘Exploring Tangible User Interface Design for Social Connection Among Older Adults: A Preliminary Review’, in Extended Abstracts of the 2023 CHI Conference on Human Factors in Computing Systems, Hamburg, Germany, 2023.
[2] Y. Liu and R. Tamura, ‘How can smart home help “New elders” aging in place and building connectivity’, 07 2020, pp. 100–107.
[3] P. Bhowmick and E. Stolterman Bergqvist, ‘Exploring Tangible User Interface Design for Social Connection Among Older Adults: A Preliminary Review’, in Extended Abstracts of the 2023 CHI Conference on Human Factors in Computing Systems, Hamburg, Germany, 2023.
Since my last update, I’ve been trying to pay more attention to how older adults actually use their phones. One thing that I found interesting was that many of them were actually very comfortable using WhatsApp. They understood what was happening, could explain different functions and generally navigated the app without too many problems.
While observing these interactions, I started thinking about whether some of the actions older adults struggle with could be simplified. Instead of trying to redesign entire interfaces, what if I could take specific tasks or frequently used functions and break them down into a much simpler interaction?
This led me to explore more tangible interactions, specifically NFC technology. Most smartphones already support NFC and I got some inspiration by some already existing products like the ENA Care, which use physical objects to trigger digital actions. The idea of replacing complex digital interactions with simple physical actions seemed actually interesting.
It actually took me some time to figure out what I wanted to focus on more. To get there, I started experimenting and creating some small prototypes.
My first step was to try out an NFC-based tangible interaction system myself. Luckily, I already had some NFC tags and cards lying around at home.. Before getting started, I did some research and found that there are already many tutorials explaining how to set up NFC routines on smartphones. One resource I found particularly helpful was: https://www.wakdev.com/en/apps/nfc-tools-android.html
Setting everything up was actually much easier than I expected because most smartphones already support reading and writing NFC tags. Using some old NFC cards I had at home, I created my first simple prototype based on existing NFC automation. This initial experiment helped me understand possible ways of interaction for digital tasks for older adults.
The first thing I had to figure out was which tools I could use for working with NFC tags. After some research, I decided to use NFC Tools by Wakdev writing the tags. Additionally, I had to install another app called NFC Tasks, also by Wakdev, to create automated actions.
However, while setting everything up, I already started thinking about older and less experienced users. Even though the process was easy for me, I don’t think many older adults would be able to configure such a system on their own. This made me think that there might be a need for an all-in-one application that simplifies the setup and guides users through it.
After getting the technical side working, I started experimenting with the interaciton. Since the NFC tags I had at home were just small stickers, I wanted to create a more tangible and easier way to interact with them. In my case I thought of basically two ways of using NFC: either bringing the NFC tag to the phone or bringing the phone to the NFC object. To try this, I designed and 3D printed several different variants that I would like to test further.
While prototyping, I ran into a few problems. One thing I noticed was that the distance between the NFC tag and the smartphone can’t be very large, meaning the tag has to be placed almost directly on the surface of the object. The more I thought about it, the more I realized that small physical objects might not be ideal for older adults. They can be difficult to pick up, especially for elderly people and they also need to be stored somewhere. On top of that, they could easily get lost.
While experimenting with these prototypes, I came up with an idea: creating a physical phone book based on NFC interactions. Instead of navigating through contacts and menus, users could simply hold their phone to a physical card or object and immediately call them. In addition, this phonebook could also contain other tasks.
1.Have you ever followed a map and reached your destination… but don’t remember the way? I want to explore a mobile navigation app that focuses not only on speed, but on experience. We move fast, we arrive quickly — but we don’t really experience the city anymore.
2.Today, navigation is designed for speed. We follow instructions immediately, choose the shortest path, and rarely stop. Cities and interfaces both push us into constant movement — leaving little space to pause, notice, or reflect.
3.What if navigation was not only about getting from A to B, but about experience?
I’m exploring a map system that suggests routes based on mood, time, and curiosity —
encouraging slower, more intentional movement through the city.
4.This approach reframes navigation as an experience, not just a tool. It supports slower, more mindful movement and helps people build a deeper, more personal connection with the city.
5.My curiosity grows from urban studies, movement, maps, and outdoor exploration. I’m interested in how we experience cities — and how design can gently shift the way we move through them.
Design & Research 2 | For: Katerina Sedlackova
In our last class of Design and Research II with Katerina Sedlackova, we practiced crafting elevator pitches using a structured framework. Here is the pitch I developed for my concept:
The Pitch
We’re living in an era where everyone is a ‘photographer,’ but nobody actually knows how to use a camera. We’ve traded the craft of photography for a ‘smart’ button that does all the thinking for us.
The problem is that cameras are now so good, they’ve made the person behind the lens irrelevant. The AI chooses the light, the blur, and the mood. It’s a great image, but it isn’t your craft — it’s just a software output.
I’m building Photography Co-Pilot. It’s an AI that stops taking the photo for you and starts teaching you how to do it yourself. It explains the manual settings in plain English, in real-time, so you can take back creative control.
While everyone else uses AI to replace the artist, I’m using it to empower the artist. I’m giving the craft back to the person behind the lens.
I’m a designer and photographer. I believe technology should help us learn a skill, not replace the need for one.