Target Audience: Developers, UX Designers, Business Analysts, SAP Architects
Reading Time: 5 minutes

Let’s look at how we use our phones at work today. We check reports on the go, approve requests between meetings, and look up customer details on the way to the next appointment. Our phones have quietly taken over as the primary work device and enterprise apps are still trying to keep pace.

But there’s one interaction that still slows us down: filtering data.

Picture a familiar scenario: You’re heading for a meeting and want to quickly check for overdue invoices above 10,000 EUR. You open the app, ready to get the number. A few minutes later, you close it and tell yourself you’ll check from your desk later.

If that sounds familiar, you’re not alone.

In this article, we’ll explore:

• Why mobile filtering has felt like a workaround for so long
• What the industry has tried, and where those approaches fall short
• What users have really been asking for
• How a new approach in SAP Fiori elements is finally delivering the experience that users deserve

Let’s take a closer look.

Why Mobile Filtering Falls Short

Filtering on a mobile phone has always felt more like a workaround than a workflow. And the reason is simple: filter bars were designed for desktops, not for a device meant to fit in the palm of your hand. When we take the same filter bar and place it on a 6-inch screen, even the best-designed applications end up delivering a subpar experience.

It’s not that users can’t filter on mobile phones. They can. It’s just that the experience makes it far harder than it needs to be.

Where the Experience Breaks Down

Users filtering on mobile phones run into the same usability issues, regardless of how well the application is designed. Here’s what typically gets in the way:

• Labels too small to read comfortably
• Tightly packed dropdowns that lead to incorrect selections
• Date pickers demanding exact input
• An Apply button that isn’t visible without scrolling

The result is almost the same. The user gives up the task and waits until they’re back at their desk. 

For a mobile-first workforce, this isn’t a small inconvenience. It’s a real barrier to getting work done.

What We’ve Tried Before

The mobile filtering problem isn’t new. Over the years, the industry has tried several ways to solve it. Each approach has moved the needle a little, but none has fully solved the problem.

Here are the most common approaches and where they fall short:

• Responsive design: Stacks filter fields vertically to fit small screens. The layout improves, but the underlying complexity remains. Users still work through the same dense form, only with more scrolling.
• Simplified filter sheets: Removes advanced filtering options and retains only the basics. The UI feels cleaner, but users lose the depth and precision they need for real business scenarios.
• Quick filters: Offers predefined options for common use cases such as “My Open Items” or “Due This Week“. They work well for predefined scenarios, but the moment users demand something ad-hoc, the approach breaks down.

What Users Actually Want

A clear pattern emerges when we watch how users interact with filters on their mobile phones. They don’t want to configure the filter bar or tap through dropdowns. What they want is simple:

“Just let me describe what I’m looking for.“

This single expectation captures the change users have been waiting for. And it is exactly the experience the AI-powered natural language filter delivers.

From Filter Bars to Conversations

That’s exactly what the new AI-powered natural language filter in SAP Fiori elements is built to deliver. Instead of selecting values in complex filter forms, users can simply type or speak what they’re looking for. A simple phrase like “overdue invoices above 10,000 EUR” is all the AI needs.

Behind the scenes, the AI understands the intent, aligns it with the application context, and translates it into a precise OData filter. This is the same kind of filter the application would’ve applied if the user had gone through the traditional filter bar. The results appear on screen, filtered exactly as the user described.

The best part is that this capability works on top of your existing SAP Fiori elements applications.

Join the Early Adopter Care (EAC) Program

Our EAC Program offers early access to the AI-powered natural language filter in SAP Fiori elements mobile phone optimization. Onboarding takes just a few steps:

1. Enroll through your SAP account executive
2. Contact the SAP EAC team
3. Align your IT organization on adoption
4. Access the experience from your mobile using the Joule Work app

What’s Next in This Series

In the next article, we’ll go under the hood and explore:

• The three-stage architecture
• The types of queries it understands
• Voice input support
• Privacy and security foundations

Stay tuned!

Sign up and share your feedback: SAP Customer Influence

Have questions or thoughts? Drop a comment below.

Vignesh Sathi Srikumar is an Engineering Lead on the SAP UX Foundation team. Connect on LinkedIn.

 Target Audience: Developers, UX Designers, Business Analysts, SAP ArchitectsReading Time: 5 minutesLet’s look at how we use our phones at work today. We check reports on the go, approve requests between meetings, and look up customer details on the way to the next appointment. Our phones have quietly taken over as the primary work device and enterprise apps are still trying to keep pace.But there’s one interaction that still slows us down: filtering data.Picture a familiar scenario: You’re heading for a meeting and want to quickly check for overdue invoices above 10,000 EUR. You open the app, ready to get the number. A few minutes later, you close it and tell yourself you’ll check from your desk later.If that sounds familiar, you’re not alone.In this article, we’ll explore:Why mobile filtering has felt like a workaround for so longWhat the industry has tried, and where those approaches fall shortWhat users have really been asking forHow a new approach in SAP Fiori elements is finally delivering the experience that users deserveLet’s take a closer look.Why Mobile Filtering Falls ShortFiltering on a mobile phone has always felt more like a workaround than a workflow. And the reason is simple: filter bars were designed for desktops, not for a device meant to fit in the palm of your hand. When we take the same filter bar and place it on a 6-inch screen, even the best-designed applications end up delivering a subpar experience.It’s not that users can’t filter on mobile phones. They can. It’s just that the experience makes it far harder than it needs to be. Where the Experience Breaks DownUsers filtering on mobile phones run into the same usability issues, regardless of how well the application is designed. Here’s what typically gets in the way:Labels too small to read comfortablyTightly packed dropdowns that lead to incorrect selectionsDate pickers demanding exact inputAn Apply button that isn’t visible without scrollingThe result is almost the same. The user gives up the task and waits until they’re back at their desk. For a mobile-first workforce, this isn’t a small inconvenience. It’s a real barrier to getting work done.What We’ve Tried BeforeThe mobile filtering problem isn’t new. Over the years, the industry has tried several ways to solve it. Each approach has moved the needle a little, but none has fully solved the problem.Here are the most common approaches and where they fall short:Responsive design: Stacks filter fields vertically to fit small screens. The layout improves, but the underlying complexity remains. Users still work through the same dense form, only with more scrolling.Simplified filter sheets: Removes advanced filtering options and retains only the basics. The UI feels cleaner, but users lose the depth and precision they need for real business scenarios.Quick filters: Offers predefined options for common use cases such as “My Open Items” or “Due This Week”. They work well for predefined scenarios, but the moment users demand something ad-hoc, the approach breaks down.What Users Actually WantA clear pattern emerges when we watch how users interact with filters on their mobile phones. They don’t want to configure the filter bar or tap through dropdowns. What they want is simple:”Just let me describe what I’m looking for.”This single expectation captures the change users have been waiting for. And it is exactly the experience the AI-powered natural language filter delivers.From Filter Bars to ConversationsThat’s exactly what the new AI-powered natural language filter in SAP Fiori elements is built to deliver. Instead of selecting values in complex filter forms, users can simply type or speak what they’re looking for. A simple phrase like “overdue invoices above 10,000 EUR” is all the AI needs.Behind the scenes, the AI understands the intent, aligns it with the application context, and translates it into a precise OData filter. This is the same kind of filter the application would’ve applied if the user had gone through the traditional filter bar. The results appear on screen, filtered exactly as the user described.The best part is that this capability works on top of your existing SAP Fiori elements applications.Join the Early Adopter Care (EAC) ProgramOur EAC Program offers early access to the AI-powered natural language filter in SAP Fiori elements mobile phone optimization. Onboarding takes just a few steps:Enroll through your SAP account executiveContact the SAP EAC teamAlign your IT organization on adoptionAccess the experience from your mobile using the Joule Work appWhat’s Next in This SeriesIn the next article, we’ll go under the hood and explore:The three-stage architectureThe types of queries it understandsVoice input supportPrivacy and security foundationsStay tuned!Sign up and share your feedback: SAP Customer InfluenceHave questions or thoughts? Drop a comment below.Vignesh Sathi Srikumar is an Engineering Lead on the SAP UX Foundation team. Connect on LinkedIn. Read More Technology Blog Posts by SAP articles 

#SAPCHANNEL