Tag: Emerging Trends

WhatsApp Taxi

You need a taxi. Instead of calling or using a dedicated app, you open WhatsApp, share your location, and place the order by message. Taxi Deutschland positions “WhatsApp Taxi” as a simple way to request a cab in major German cities using the behavior people already know. Messaging.

Why this shows up now

After years of public sharing and transparency on social media, people gravitate toward more intimate, private, and even anonymous ways to communicate. That shift boosts the popularity of messaging apps and ephemeral messaging. Chat apps become hubs for social networks, games, e-commerce, and more.

The service. Taxi ordering by location message

Taxi Deutschland launches a new service called “WhatsApp Taxi” that allows users in major German cities to order a taxi by simply sharing their location via a WhatsApp message. The interaction is reduced to one core input. Your location.

The pattern. Messaging becomes an interface

Just last week I wrote about how KLM was starting to use Facebook Messenger for customer service related queries and tasks. WhatsApp Taxi sits in the same movement. Utility shifts into the messaging layer, which means the chat app becomes the place where the service starts, is confirmed, and is updated. The chat thread becomes the service surface.

In service categories where the audience already coordinates through chat, the smarter move is often to reduce entry friction rather than build another interface.

Why this lands for service adoption

This is a stronger service design move than another branded utility app because one familiar message and one high-confidence input make the service easier to try, which is why the interaction feels lighter and more repeatable.

Extractable takeaway: When the job to be done can be triggered with one trusted input inside a familiar chat flow, messaging can outperform a dedicated interface on adoption because it removes setup and learning cost.

The real question is whether your service needs a dedicated interface at all when messaging can already handle the request, confirmation, and follow-up. For Taxi Deutschland, the business intent is to reduce ordering friction and capture demand inside an existing behavior instead of forcing a new app habit.

What service brands can lift from WhatsApp Taxi

  • Ship in the behaviour people already have: If your audience already lives in messaging, put the service where the habit already exists.
  • Reduce the request to one high-confidence input: Location-first is a clean pattern when the service is fundamentally “come to me”.
  • Make chat the interface: Treat the thread as the order surface. Request, confirmation, updates, and support stay in one place.
  • Keep the interaction minimal: If one message can start the service, adoption is easier than “install app, register, learn UI”.
  • Design for repeat use: The same simple flow should work the second time without needing new learning or setup.

A few fast answers before you act

What is WhatsApp Taxi?

A Taxi Deutschland service that lets users order a taxi via WhatsApp by sharing their location in a message.

Where does it work?

Taxi Deutschland positions the service for use in major German cities.

What is the core user action?

Send your location via WhatsApp message to initiate the taxi order.

Why is this a marketing and product signal?

It shows how messaging apps evolve from communication tools into utility layers where services can be initiated and managed.

What is the transferable lesson for brands?

If your service can be reduced to a small set of high-confidence inputs, messaging can become a low-friction interface that people already understand.

Corning: A Day Made of Glass

Here is a future vision video by Corning, on where they see multi-touch digital displays over the next few years. Multi-touch means the surface can track several fingers or hands at once, so gestures like pinch, rotate, and shared interaction become natural.

What the film is really demonstrating

The core mechanic is simple. Turn glass from “protective cover” into “primary interface”. Every surface becomes a screen. Every screen becomes responsive to direct manipulation. Information follows you across contexts, from home to school to office, with the same touch-first language, meaning a shared set of gestures and feedback that stays consistent across devices.

In consumer electronics and workplace IT, concept films like this are used to align designers, suppliers, and product teams around a shared interface direction.

The real question is whether your interaction language can stay consistent as screens spread across surfaces and contexts.

Treat the glass as incidental. The interaction model is the product.

Why it lands

It removes the usual friction between people and devices. No boot-up rituals, no “find the remote,” no hunting through menus. You touch the thing you want to change, and the system answers in place. That immediacy is the real promise, not the glass itself. Because the system responds at the point of intent, it reduces both cognitive load and coordination cost in multi-screen tasks.

Extractable takeaway: When you are pitching a new interface paradigm, show behavior before hardware. Make the gestures, feedback loops, and handoffs between screens unmistakable, so the idea remains valuable even if the materials and form factors change.

What to steal for your own work

  • Design the interaction language first. Define the small set of gestures and responses that can travel across surfaces, sizes, and contexts.
  • Keep information anchored to the object or task. The winning moments happen when data appears exactly where the decision is being made.
  • Plan for multi-user moments. Big surfaces invite collaboration. Design for two people at the same time, not just one user plus spectators.
  • Prototype the “seams.” The handoff between phone, table, wall, and car is where most visions break. That is the first place to test.

A few fast answers before you act

What is “A Day Made of Glass” trying to communicate?

It is a vision of glass becoming an interactive medium, where touch-first displays move from dedicated devices into everyday surfaces.

What’s the practical value of watching concept videos like this?

They are useful for spotting interface patterns early, then translating the patterns into near-term prototypes and roadmap language for teams and partners.

What’s the biggest product risk in “glass everywhere” thinking?

Over-indexing on the surface and under-investing in the interaction model. If the gestures, feedback, and context switching are weak, the material does not matter.

What is one immediate takeaway a UX or product team can apply?

Write a short “interaction grammar” for your experience, then test it across at least two form factors. If the grammar does not travel, the concept will not scale.

Who should use this kind of vision film internally?

Use it when you need to align design, product, and IT partners on a shared interaction direction before you lock hardware decisions.