Users were paying for an Aptoide product on a screen that didn't look like Aptoide. The real problem was a trust gap at the most fragile moment in the funnel, the payment step, not a tired logo.
The Aptoide Wallet powers in-app purchases, rewards, and time-limited bonuses for mobile gamers in the Aptoide ecosystem. Since its launch in 2018 it shipped as AppCoins Wallet, a leftover from the company's earlier bet on an Ethereum ERC-20 token. When the strategy moved away from crypto, the brand stayed behind: a wallet promoted inside the Aptoide store but rendered in a visual language that read as a different company.
Why this was a UX problem
A rebrand is easy to treat as just a visual job. But this one mattered because users were paying for a misaligned identity:
Every time users hit the wallet surface, they had to make a small leap of faith: "is this still Aptoide? am I safe to pay here?" That's a trust problem, and trust problems live in the UX layer, not the brand book.
There was a quieter complication too: the AppCoins name carried associations users had already formed, some neutral, some shaped by crypto's reputation. The rebrand had to do two things at once: build the new identity, and retire the old one without making existing users feel orphaned. That made "ease of recognition" a continuity guarantee, not just an aesthetic goal.
Anchoring the project in user-facing outcomes
Before sketching anything, I reframed the brief from "make a new logo" into four outcomes a user could feel:
| Outcome | What the user should feel |
|---|---|
| Communicate the value proposition | "This wallet is built for me, for gaming." |
| Coherence with the Aptoide ecosystem | "This is still Aptoide. I already trust them." |
| Consistency across touchpoints | "I recognise this wherever I see it." |
| Easy to apply internally | "It looks polished even when a non-designer ships it." |
Research: auditing the existing identity
I mapped every place an Aptoide identity already lived: the app store, sub-products like the Smart TV variant and the APK uploader, Aptoide Connect (recently rebranded from Catappult), and the AppCoins/AppCoins Wallet pair.
The pattern was clear: every product pulled back into the Aptoide brand (Connect being the most recent) had benefited from the alignment. AppCoins Wallet was the outlier. A transaction that started inside an orange app store ended on a screen that looked like a different company entirely.
So we decided: the wallet's new identity would not be a free-standing brand. It would be a visible member of the Aptoide family, borrowing equity from the parent rather than competing with it for recognition.
Defining the values
We ran a survey through a digital platform to find the values that mattered most and how to rank them. A flat list wasn't enough, so we forced them into a clear order. When two values clash in a design decision, the ranking tells us which one wins.
| Priority | Value | UX implication |
|---|---|---|
| 1 | Rewarding | Surface bonuses and level-ups visibly; make the perk legible |
| 2 | Trust | Lean on the parent brand; signal safe payment methods |
| 3 | Fun | Visual language should feel native to gaming, not banking |
| 4 | Global | Localised payment methods, no Google Mobile Services dependency |
| 5 | Fairness | Communicate the smaller developer cut and user rewards |
So we decided: trust outranking fun gave us our most important rule. When "feels gaming-native" and "feels like Aptoide" pulled in opposite directions, Aptoide won. Fun shows up in the supporting elements (colour, motion, secondary symbol); trust shows up in the load-bearing ones (the wordmark, the primary colour relationship).
Brand architecture as an IA decision
The next question was strategic: should the wallet be a House of Brands (independent identities under one parent) or a Branded House (everything visibly part of the same family)?
I studied a spread of Branded House implementations (Google, BBC, Atlassian, FedEx, Microsoft), but two mattered most for the decision:
- FedEx sits at the strict end. Same wordmark, with only the suffix and a colour shift signalling the sub-product (FedEx Express, FedEx Ground). The lesson: a single anchor element, repeated faithfully, can carry an entire family. The risk: every sub-product feels interchangeable.
- Coinbase + Coinbase Wallet is the most direct analogue, a consumer-facing parent brand with a wallet sub-product. They keep the wordmark structure consistent but give the wallet its own colour and a distinct symbol. The lesson: a wallet can have its own personality without breaking the family relationship, as long as the wordmark and one shared cue stay constant.
Every successful Branded House had at least one shared cue, a colour, a shape, or a tone, doing the recognition work before the user consciously read a logo.
So we decided: Aptoide Wallet would borrow Coinbase's structural lesson (consistent wordmark + distinct sub-brand colour) and FedEx's discipline (one shared cue, applied without exception). The shared cues would be the VAG Rounded wordmark, the Aptoide orange as the anchor, and a shape borrowed from the Aptoide glyph.
Mood and competitive analysis
For the gaming-native side of the identity, I looked at brands the target audience already loves: Twitch, GOG, EA Play, Steam and the Steam Deck.
A pattern emerged: purple dominates the gaming category. Some research backs this up: purple is associated with creativity, mystery, and rarity, which align with how gamers describe what they want.
So we decided: purple becomes the wallet's secondary colour. Orange stays primary (that's the family anchor), purple does the category-signalling work. A user reading the wallet at a glance gets two messages at once: "this is Aptoide" and "this is for me, the gamer."
The new identity
The concept that survived all four constraints reuses two of Aptoide's strongest cues (the orange and the symbol) and merges them with a gaming-native shape: a lightning bolt, the universal "power-up" icon.
A few decisions worth calling out:
The lightning symbol borrows a shape from the existing Aptoide glyph. A small detail, but the kind of visual rhyme that makes a brand family feel like a family, even when a user couldn't say why.
A tricky distinction: Wallet vs. Balance
The messiest UX problem in the project wasn't the logo at all. It was a one-letter-off conceptual collision:
- Aptoide Wallet: the product. Where users pay, manage, and configure.
- Aptoide Balance: a feature inside the product. The bonus credit users earn through gamification and spend on in-app purchases.
The previous identity treated these as two parallel visual concepts, each with its own mark. Internally that made sense: they're different things. To the user, it created a problem.
This played out in concrete moments:
- A user sees a payment-method picker that lists "Aptoide Balance" with one icon, and elsewhere sees the "Aptoide Wallet" with a different icon. Are these the same thing? Different things? Are they competing?
- A push notification says "You earned 50 credits to your Aptoide Balance" with one mark; the user opens the app and sees the Wallet mark instead. The continuity breaks.
- An app store listing shows the wallet mark; the in-app purchase confirmation shows the balance mark. The user has paid in the same flow but sees two visual identities.
So we decided to collapse it: one symbol, one brand, with a documented usage rule.
| Surface | Old approach | New approach |
|---|---|---|
| Payment method picker | Separate "AppCoins Wallet" + "Bonus" entries with different marks | One Aptoide Wallet mark; "Balance" appears as a labelled sub-amount |
| Push / email notifications | Mark depends on whether topic is wallet or balance | Always the wallet mark; balance is a noun in the copy, not a brand |
| Earned-credit moments | Bonus mark with celebratory styling | Wallet mark with the lightning glyph emphasised; same family, contextual emphasis |
The user now learns one mark. The relationship between Wallet and Balance lives in copy, where it can be explained, rather than in two visual identities the user has to reconcile.
Cross-platform application
The wallet is now platform-agnostic, across Android, iOS, and a web payment flow. So the identity has to read as "Aptoide" regardless of where the user landed:
UI changes were kept minimal. They weren't part of the rebranding scope, and bundling them in would have blown the timeline. A lesson I keep relearning: a focused brand refresh that ships beats a perfect overhaul that doesn't.
Brand in the wild
With the identity locked, the next step was proving it held up outside a Figma file: applied to real surfaces, in real contexts, by people who weren't the designer who made it. App store banners, social posts, in-product illustrations, promotional copy. Each one is a stress test.
The identity passed. The orange and the lightning symbol read as a unit. The VAG Rounded wordmark landed as "Aptoide" before the reader processed the word. The purple accent gave it the gaming-native register without pulling it away from the parent brand.
Outcomes
A rebrand resists single-metric attribution; too many other variables move at once. But the qualitative shifts showed up in the right places:
| Dimension | Before | After |
|---|---|---|
| User question at payment | "Is AppCoins part of Aptoide?" | "This is just Aptoide's wallet." |
| Marks the user has to learn | Two (Wallet + Balance), each with sub-variants | One mark, contextual usage |
| Aesthetic register | Crypto / fintech | Gaming-native |
| Identity at payment surface | Foreign: felt like a third party | Continuous: reinforces trust |
| Internal application cost | Designer required for most placements | Engineers / PMs ship on-brand without review |
| Cross-platform consistency | Drift between Android, web, and marketing | Same identity holds across iOS, Android, web |
The strongest signal isn't in any single row. It's that the wallet stopped being the surface where the Aptoide brand contract broke. Whatever conversion or trust uplift compounds from that, compounds at the most expensive point in the funnel.
Takeaways
Every visual cue a user encounters is part of their experience of the product. Treating brand and UX as separate disciplines misses the moments where they're actually the same thing, like a payment screen.
