Kalkine App Overhaul

TL;DR

The existing mobile experience had become dense, inconsistent, and harder to scan as more data and actions accumulated. Users could get to the right information, but the path was slower than it needed to be and the interface made key actions feel more complex than the underlying task.

I led a product-led overhaul focused on three things:

• clearer information hierarchy
• navigation that matched real investor jobs
• stronger trust through consistency and clearer next steps

This public version keeps the delivery logic and decision framework while leaving out confidential internal detail.

1) Context

This was a mobile experience used for repeat investor workflows such as checking alerts, scanning watchlists, and reviewing portfolio-related signals. The problem was not lack of functionality. The problem was the cost of understanding what mattered now.

In high-frequency fintech use cases, users are often trying to answer a simple question quickly:

What changed, why does it matter, and what should I do next?

The previous experience made those answers work harder than they should.

2) What was breaking down

Three patterns were getting in the way.

Information density without hierarchy

Important signals were mixed with secondary detail. Users had to scan too much before finding the part of the screen that actually influenced a decision.

Navigation that did not match core jobs

Alerts, watchlists, and portfolio views were all present, but the product structure did not consistently reflect how frequently those jobs occurred or how quickly users expected to access them.

Inconsistent patterns reduced trust

When similar data blocks behave differently across screens, people slow down. In finance, that hesitation matters because consistency is part of how the product earns credibility.

3) Product goals

The redesign effort was structured around a few product outcomes:

• make key investor tasks easier to reach and easier to complete
• reduce cognitive load in the first 5–10 seconds of a screen view
• establish repeatable UI and interaction patterns the product could scale with
• improve clarity without turning the app into an empty or oversimplified shell

4) Discovery inputs

The strongest discovery signal came from combining several lightweight sources instead of waiting for one perfect research package.

I used:

• feedback themes from support and stakeholder conversations
• product walkthroughs of the highest-traffic user journeys
• review of where hierarchy, labels, and action placement created hesitation
• comparison against the expectations users bring from other investing products

A clear pattern emerged: users did not need more information first. They needed a more trustworthy first layer.

5) The solution

Rebuild the hierarchy around decision speed

The mobile experience was reorganized so the most actionable layer appeared first. Primary signals moved higher, supporting detail became secondary, and repeated patterns were made visually consistent.

Re-center navigation around core jobs

The redesign treated alerts, watchlists, and portfolio exploration as primary investor workflows rather than secondary modules. That shift improved wayfinding and reduced the need to remember where an action lived.

Standardize components and states

A component and pattern pass made repeated UI structures more dependable across the app. That included card structure, labels, spacing, and action placement. The goal was not only aesthetic consistency. It was faster recognition.

Improve the quality of next-step cues

Each screen had to make the next likely action more obvious. Users should not have to interpret the interface before they can interpret the market information inside it.

6) Delivery approach

The work was run as a product and delivery effort, not only a visual redesign.

That meant:

• defining a tighter scope around the highest-value journeys first
• using a shared inventory of screens, components, and priority issues
• aligning design, engineering, and QA on what had to stay consistent
• treating release quality and post-launch learning as part of the work, not a handoff afterthought

This made the redesign easier to ship incrementally and easier to extend after launch.

7) Outcome

The strongest outcome was improved clarity. The product became easier to scan, easier to navigate, and easier to trust during repeat-use flows. Internally, the team also gained a more reusable product language for future mobile work.

Public-safe impact signals from the work:

• faster access to high-intent actions such as alerts and watchlist review
• less ambiguity in navigation and action placement
• stronger consistency across screens that previously felt disconnected
• better foundation for future analytics and optimization work

8) What this project reinforced

A few principles held up clearly:

• clarity is a feature in trust-sensitive products
• hierarchy matters more than volume
• navigation should reflect user jobs, not org structure
• reusable product patterns make later delivery faster and safer

9) What I would carry forward

If extending the work further, I would keep pushing on:

• stronger personalization around alert relevance
• improved instrumentation for action-oriented mobile outcomes
• progressive disclosure patterns that keep density manageable as the product grows
• tighter feedback loops between support themes and product iteration