mobile app redesign.

LumApps is a white-label collaborative intranet designed primarily for desk workers, enabling both top-down communication (from leadership to employees) and peer-to-peer communication. The existing mobile app was an extension of the web platform but was underused by the entire user base - desk workers.

To address frontline workers, a second mobile application was developed.

One of the strategic goals was to consolidate the mobile experience by eventually maintaining a single app serving both user segments, rather than two separate apps.

The existing apps were largely underused by users across the board, but accessibility was actually a strength of the mobile experience rather than a pain point. The main issue lay in fragmented features and inconsistent experiences between the two apps.

We lacked clear insights into user expectations and usage patterns, especially among frontline workers who operate under different constraints than desk employees.

We needed to:

• Understand the real mobile needs across a wide range of users.
• Reimagine an app experience tailored for mobile-first behaviors.
• Design a unified content experience that made sense for quick, on-the-go usage.
• Plan for a consolidated app to serve multiple user segments efficiently.

Redesign the mobile application, optimized for blue-collar workers and mobile-first use cases. This meant:

• Delivering a seamless, feed-first navigation experience.
• Prioritizing content consumption and lightweight interactions like starting a draft.
• Supporting the broader strategy of making LumApps inclusive of all employee profiles, not just desk workers.
• Establishing a scalable and consistent mobile Design System to unify the user experience and streamline development.

discovery.

We conducted in-depth interviews with users and non-users of the current mobile app. The participants represented a variety of countries, roles, and use cases to ensure we captured a comprehensive view of needs.

Key findings:

• Unlike the web platform, which serves 7 distinct personas, the mobile app usage was concentrated around only 2 personas.
• These mobile personas primarily needed quick access: consulting internal content or starting a draft while on the move.
• Publishing and advanced features remained tied to desktop.
• Administrative features were unanimously deemed unnecessary for mobile.

‍

‍

design.

As the design lead, I collaborated closely with the PM, mobile PO, and the UX researcher. We ran collaborative workshops with Android and iOS developers to align early on technical feasibility and constraints.

The design focused on:

• A unified feed experience, aggregating all relevant content in one place, unlike the segmented navigation of the web version.
• A navigation system tailored for quick, glanceable interactions on mobile.
• Entry points to key actions (start a draft, save for later, consult updates) that respected the constraints of mobile usage.

‍

A core objective of the project was to develop a mobile Design System that would bring consistency and scalability across platforms. Until then, mobile apps relied heavily on native OS components visually adapted to mimic web styles, which led to inconsistencies and duplicated effort.

I partnered with the web Design System lead and organized weekly syncs with the Android and iOS leads. We started by standardizing color palettes and typography before prioritizing components based on project needs and designer requests.

All components were designed in Figma and documented in Storybook, complete with usage guidelines and best practices. This initiative greatly improved design consistency and accelerated development, with an estimated 95% reduction in development time for reusable components. The mobile Design System was subsequently adopted by other projects across the company.

‍

testing.

We conducted an initial testing round by splitting participants into two groups: one tested prototype A first then B, while the other started with B before moving to A. This rotation helped minimize order bias (primacy effect), which can skew preference toward the first option shown.

The expected outcome was a balanced mix of the two versions. We then ran a second round on prototype C, which resolved the last open questions and confirmed the relevance of a unified feed along with lightweight interaction patterns.

handover.

Final high-fidelity mockups were delivered and validated by the mobile teams. Due to my departure, I was not involved in the final internal presentation or development follow-up.

A mobile application concept designed specifically for frontline workers, with:

• A radically simplified interface.
• A unified feed aggregating all company communications.
• Contextual actions suited to short mobile sessions.
• A clear split of use cases between the "consult / draft" needs on mobile and "publish / admin" features on desktop.

The project laid the foundation for LumApps’ mobile strategy for non-desk workers. It shifted the internal perception of mobile from an extension of the desktop to a standalone product with its own logic and purpose.

• Designing for mobile-first requires dropping many assumptions from the desktop experience.
• Unified navigation is critical when dealing with fragmented attention spans and short usage windows.
• Close collaboration with dev teams early in the process enabled a realistic scope and faster iteration.
• Strategic alignment on target users was essential to avoid feature creep and desktop parity pitfalls.