We handle the technology, you enjoy the freedom
GIS, layers, UX and data. Just a glimpse from a developer’s vocabulary. Technical jargon for tools like our interactive maps. We also see too often that software-related solutions focus on the technology, the building, the walls, and the architecture.
Tech jargon flies at us left and right. And that’s not even what it’s all about! Let’s be honest, it’s much more fascinating to zoom in on the many choices we as developers have made and the benefits they offer you. We’ll guide you through the technical language and applications of Wolf Maps so that you know exactly what you need now, and what to expect in the future, from your interactive map.
GIS
Perhaps you’ve heard of it during your quest for interactive maps, or perhaps not at all. GIS is a Geographic Information System that allows us to manage, analyze, and share data with others. We use that data worldwide to uncover trends, collaborate, and assess current situations. Essentially, GIS is the foundation. Without data, there is no map.
We handle the technology, you enjoy the freedom. Because the truly beautiful things need time to grow. And yes, sometimes you need complex technology for that. But ultimately, it is precisely these beautiful things that create joy and freedom. For you as a provider and for your visitors.
Layers
In the world of interactive maps, you often hear the term “layers.” I, too, am quite familiar with this term from design tools like Photoshop and Figma, and I used it in maps without a second thought. Until my partner Tim told me that, despite his technical background, he didn’t know what layers were. That got me thinking: we often assume that everyone knows what layers are, when in fact that isn’t at all self-evident.
That’s why we have chosen not to use the term “layers” anywhere in our maps. In our studio, the management environment, we do talk about categories, but for the visitor, it remains simple. They simply see handy ways to filter the map, without technical jargon getting in the way.
It’s a small adjustment in language, but one that makes a big difference in the user experience.
Infinite Possibilities with Data
When it comes to technology, things quickly become vague. The techie might understand it well, but you might not quite get it. Everything is technically possible, but do you really want that? If you’re going to build something, you need not only people who understand the technology, but also those who know about UX (user experiences). You need people who understand the target audience and the goal, people who can visualize the customer journey. Experience shows that if you’re not clear about what you want to achieve and for whom, you end up showing too much on one map. Leave that to Google; with Google, you see the whole world. And, paradoxically, nothing at all. Kill your darlings and focus on what truly matters.
Mobile First
Technology with maps that aren’t mobile in 2024 is, in most cases, poor technology. Some interactive maps are still not mobile, even though most users access a map with their phone. Wolf Maps focuses on mobile users and mobile management. We don’t use an app; we make sure that maps can be used directly in the browser. But don’t forget, the combination of online and offline is what’s truly valuable. For example, place a QR code on information panels, program booklets, or signs. In this blog, we share all the ways to share your map with your visitors.
Maintenance
Of course, you can’t avoid the technical maintenance of your interactive map. We perform back-end updates (on the technology side) at Wolf Maps, think of adding or improving features. However, all the visible management (what appears on the map) you can do entirely yourself. This way, you retain full control over your map. We ensure that the map is technically sound; you just need to fill and adjust it.
And nowadays, it’s even easier to carry out maintenance, thanks to integrations such as those with Plaece.
Sloooow
Maps that don’t fully load are a crime. Just think about how annoying it is to have to wait for a website to load. That’s why it’s important for us as developers to keep a tight grip on loading speeds. We do this by building our technology compactly, without unnecessary additions, so that the foundation of our “house” (the software) remains strong and steady.
Technology Must Be Transparent
So, whether it’s tech jargon or not, we make our technology transparent. Have you come across any technical terms or applications that you’d like explained further? Let us know, and we’ll add them to this blog.
