
Simplifying SOTI Snap’s theming: creating a seamless customisation experience
Read time: 12 mins
Role
As sole Product Designer, I led the end-to-end redesign of SOTI Snap's theming experience partnering with the team to define, iterate, and deliver a more intuitive and brand-consistent app building flow.
Team
1 product designer
1 product manager
5 software engineers
Timeline
1 month
Background
SOTI is growing day to day. It has
Let’s read this narrative
About
Limitations
Problem
Framing problem
Before diving into the problem statement, let’s first understand the core issues through the video and key observations below.
Limited product capabilities
Time-consuming manual effort
Updating icons and colours across every screen feels like a repetitive, manual burden.
There is no way to apply changes globally, making the process slow and inefficient.
What should be a quick task ends up consuming significant time, hindering productivity.
Mental modal mismatch
Non-tech-savvy users expect a simple interface that allows them to easily customise the appearance of their app. However, the current system's limited and rigid functionality creates confusion.
Fragmented user journey
Problem Statement
Non-tech-savvy users find app customization confusing and time-consuming due to limited and rigid theming capabilities.
Identifying the opportunity
Our goal
How to reach our goal?
How to measure feature success?
Planning the approach
a. Define the anatomy
b. Competitive benchmarking
Templates preview from FigJam:

Full screen view from Mobbin:

Theme builder from Flutterflow:

c. UX baseline establish

Initial wireframing




Before moving into high-fidelity design, "I walked stakeholders through the wireframes in a pre-grooming session presenting the full feature scope, explaining the design rationale, and opening the floor for early discussion".
The goal was simple: catch misalignments early, not after pixels were polished.
Development-related queries were handled directly by the Dev Manager, keeping the conversation focused and the right people accountable for the right decisions. This collaborative structure ensured smoother handoffs and avoided back-and-forth later in the process.
Refining the Vision
Step 1 (Basic details)
This step cover information like App name, its logo and description.
Step 2 (Choose a theme)
Initially, we planned to combine template and theme selection into a single step. In this flow, the user first selects a theme from the left panel and then chooses the corresponding template.
Template preview
A template preview where users can browse all mobile screens within a template and select the ones they want to include in their design.
Step 3 (Canvas)
After setting basic details and selecting a template and screens, users will land on the App Builder, where they can further customize their UI. A new Theme tab has been added to the left navigation bar for global settings. The right property panel now updates dynamically based on the new theme settings.
Choose a color
For example, when users want to change a color, they can select it from the property panel or adjust it in the global theme settings. There will be a clear distinction between theme colors and custom colors they add.
Add typography style
Same for typography setting there will be proper bifurcation between custom style and theme style.
Choose an icon
Users can choose from a set of default icons to maintain a consistent UI. If they have their own icon collection, they can upload it under Custom Icons in the Global Settings page.
Typography
The first tab is Typography, where users can manage font settings for responsive design. By default, a pre-set typography style is provided, including font family, size, spacing, weight, an italic switch, and an underline switch. Users have the flexibility to customize these settings and can reset them to default.
Colours
The second tab, Colors, allows users to manage color settings for both light and dark modes. A live screen preview helps them see how colors fit their theme in real time. Users can add new colors to customize their theme further and edit existing color codes.
Icons
In this Icons tab, users can customize the appearance of their icons. They can easily select a primary color to match their branding and upload custom SVG files to personalize icons further.
Spacing
In this Spacing tab, users can adjust the spacing between elements to fine-tune their layout. They can set different spacing values for margins and paddings and choose their preferred unit of measurement (e.g., px, em, rem).
Design Feedback

Stakeholder: "Theme selection should be removed from onboarding, it's already available inside the platform."
Design pushback: "Removing it upfront would cause users to miss setting the right context from the start."
Middle ground: Keep it in onboarding but simplify it, so it feels natural rather than redundant.

Users can face a cluttered onboarding flow when selecting pages for their project, as the select screen competes with other setup steps.


Oversized Color Cards
Back to artboard
Prototype
Click on "expand" icon to see full view prototype.
Expected impact
This feature has been designed and handed off to development. As it is planned for the 2027.0 release, the following outlines the expected impact, which will be measured post-launch.
Efficiency / Time-to-Complete
Average time to complete the theming setup flow. The core problem was slowness; this proves (or disproves) the redesign fixed it
Number of screens where users manually override a theme color. Lower means global theming is working as intended
Task completion rate for the end-to-end theming flow. To catch where users drop off and what still needs fixing
Feature Adoption
% of active SOTI Snap users who engage with the new theming panel within 30/60/90 days of launch. To confirm the feature is discoverable and being used, not just shipped
% of new apps created using a template. To validate that the template library is reducing the "blank canvas" barrier
% of apps with a theme applied vs. left at default. To measure whether users are actually customising, not abandoning the flow
User Satisfaction
NPS delta among theming users vs. non-users. To connect the feature directly to overall product sentiment
Reduction in support tickets related to branding/customisation. A quieter support queue signals fewer pain points
Product Stickiness
Return visits to the theming panel. One-time use suggests novelty; repeat use suggests real workflow value
Number of custom themes saved per workspace over time. Growth here means users are investing in the feature, not just trying it
Next Steps to be taken…
Final takeaways
Continuous feedback throughout the process helped me better understand user needs and translate them into practical, impactful design decisions. Following are some more key takeaways.











