Objectuve Logo Refresh: Strategic Exploration
March 2026 — Pre-launch brand alignment
Why Now
The current Objectuve logo was designed in 2018. Back then, the product was a different thing — a simpler idea, an earlier aesthetic, a smaller ambition. Since then, everything around the logo has evolved:
- A full visual identity emerged: the blue-to-cyan gradient (
#177bbb → #05cbfc), Outfit + Inter typography, glassmorphism cards, gold achievement accents - The product found its philosophy: anti-social, action-over-consumption, gamification as core mechanic
- The brand voice sharpened: coach-who's-also-a-friend, brief, action-forward, celebratory without being hollow
- A public launch is approaching (Summer 2026)
The logo hasn't kept up. It's the last piece of 2018 still facing outward.
This document is a thinking exercise — not a creative brief, not a spec. It maps the territory, identifies the real constraints, and surfaces the decisions that matter most before any design work begins.
Where We Are Today
The Legacy Logo
The current logo exists only as raster PNGs — no SVG source, no scalable version. It lives in ionic_frontend/src/assets/legacy/ (deleted 2026-03-29 once V11 shipped — see Logo rationale) across six variants (light, dark, white, black, icon-only). The marketing site uses the same PNGs at marketing_landing/images/.
What it communicates: The legacy mark reads as functional and utilitarian. It served the product when it was smaller, but it doesn't carry the energy, polish, or personality that the rest of the brand now has. The app's UI, color system, and typography have all outgrown it.
What's working:
- The name "Objectuve" itself is strong — distinctive, meaningful (objective + vue), and memorable
- Users recognize it, and there's accumulated equity in the name even if not in the mark
What isn't working:
- No SVG source means it can't scale cleanly or adapt to new contexts
- Doesn't reflect the current visual language (gradient, glassmorphism, Outfit typography)
- Feels disconnected from the gamification identity that defines the product
- Doesn't hold up at small sizes (favicon, app icon) with the clarity modern mobile demands
- No dark mode variant was designed intentionally — the white version was a quick adaptation
Where It Appears
The logo touches every surface of the product. A refresh means updating all of these:
App (ionic_frontend)
| Surface | File(s) | Notes |
|---|---|---|
| Mobile header | src/components/ui/AppHeader.vue | Switches light/dark via useTheme() |
| Side navigation | src/components/SideMenu.vue | Full wordmark (expanded) + icon (collapsed) |
| Sign-in / Sign-up | src/views/SignIn.vue, SignUp.vue | Brand moment for first impression |
| Onboarding wizard | src/views/welcome/SlideWizardLayout.vue | First-run experience |
| Settings | src/views/Settings.vue | — |
| Favicon | public/favicon.png (557 KB!) | Oversized, needs proper multi-size set |
| PWA icons | public/statics/icons/ | 9 sizes from 72x72 to 512x512 |
| iOS app icon | ios/App/App/Assets.xcassets/AppIcon.appiconset/ | Single 1024x1024 source |
| Android app icon | android/app/src/main/res/mipmap-*/ | Adaptive icon (foreground + background layers) |
Marketing site (marketing_landing)
| Surface | File(s) | Notes |
|---|---|---|
| Navigation header | All pages | Objectuve-logo.png at 170x34 |
| Footer | All pages | Objectuve-logo-white.png |
| Favicon | All pages | 16x16 and 32x32 PNGs |
| OG/social cards | Meta tags | Currently uses a dashboard screenshot, not logo |
Other
| Surface | Location | Notes |
|---|---|---|
| Documentation site | docs/public/ | Logo SVG + PNG + icon variants |
| Design system / Storybook | design_system/public/ | logo-icon.svg, favicon |
What the New Logo Needs to Do
Represent the Brand Today
The logo must feel like it belongs in the same family as the app's UI. Right now, if you put the logo next to a glassmorphism card with the blue-cyan gradient and Outfit typography, they look like they're from different products. The new mark should feel native to the visual system.
Work Everywhere, At Every Size
This is the hardest technical constraint. The logo needs to hold up across an extreme range:
- 16x16 px — browser favicon (only a few pixels to work with)
- 44x44 px — iOS tab bar, Android notification icon
- 120x120 px — app icon on home screen
- 1024x1024 px — App Store / Play Store listing
- Full-width — marketing site hero, presentation decks
- Monochrome — single-color contexts (watermarks, embossing, receipts)
- Dark on light and light on dark — both are first-class in the app
This almost certainly means the logo is a system, not a single asset: an icon mark that works independently, a wordmark, and defined lockups for different contexts.
Signal the Right Category
Users should get a sense of what Objectuve is from the mark alone — or at least not be misled. The logo should suggest personal growth, forward progress, or achievement without being so literal that it becomes clip-art. A target, a checkmark, or a trophy would be too on-the-nose. But a completely abstract geometric shape might not signal anything at all.
The sweet spot: a mark that hints at intentionality and progress, that becomes meaningful once you know what the product is, and that doesn't pigeonhole the brand.
Carry the Tonal Qualities
The brand voice is: modern, confident, playful-not-childish, action-forward, brief. The logo should feel the same way. It should look like it belongs to a product that's serious about what it does but doesn't take itself too seriously. Premium without being corporate. Energetic without being noisy.
Differentiate
The goal/habit tracking space is crowded. The mark needs to stand on its own shelf, not blend into a lineup of similar-looking app icons.
Brand DNA to Encode
These are the raw materials — the identity elements the logo should draw from (not all at once, but selectively):
Color System
- Primary gradient:
#177bbb → #05cbfc(blue → cyan) — the brand's signature - Accent orange:
#f28529— energy, CTAs, warmth - Achievement gold:
#fcc419— reward, progression, status - Success emerald:
#10b77f— completion, positive outcomes - Midnight:
#0B0E17— dark mode base, depth
The gradient is the strongest color signal. Any color treatment of the logo should feel at home with #177bbb → #05cbfc.
Typography
- Outfit (headlines, 600-800 weight) — geometric, modern, tight letter-spacing
- Inter (body) — clean, neutral
The wordmark should either use Outfit directly (maintaining brand consistency) or a custom letterform that shares Outfit's geometric DNA.
Gamification Identity
Streaks, XP, badges (Common / Rare / Epic / Legendary), ranks (Open Road → Horizon). The building/stacking metaphor: small efforts accumulating into something lasting. This is core to the product — the logo could nod to progression, accumulation, or achievement without being literal about it.
The Name
"Objectuve" = objective + vue. There's an embedded duality: clarity of purpose (objective) and the act of seeing/perceiving (vue). The "O" is a natural focal point for a monogram or integrated mark. The "uve" suffix is distinctive and could be a typographic design opportunity.
Philosophy
Anti-social: brief, action-oriented, respectful of the user's time. The logo should feel the same way — no unnecessary flourish, no visual noise, purposeful and clean.
Strategic Directions
Five conceptual territories to consider. These are described, not designed — they're starting points for exploration, not finished ideas.
Direction 1: The Custom Wordmark
Core idea: The wordmark IS the logo. No separate icon — the typography itself is the identity, with enough character in the letterforms that it works as both text and mark.
How it connects: This is the Stripe/Notion/Linear approach. It says "we're confident enough in the name that we don't need a symbol to explain ourselves." It aligns with the anti-social philosophy: no excess, no decoration, just the thing itself.
Typographic opportunities:
- Custom ligatures or modified letterforms within "Objectuve" — the "O" could have internal geometry (a subtle ring, a facet, a dot) that works as a favicon when extracted
- The "bj" connection is unusual in English and could be designed to flow distinctively
- The "uve" suffix could carry a different weight or color treatment to highlight the name's etymology
Strengths:
- Maximum elegance and simplicity
- The name does the heavy lifting (it's a good name)
- Scales beautifully from favicon to billboard
- Timeless — custom wordmarks age better than trendy icon styles
- Easy to maintain consistency across surfaces
Risks:
- The app icon becomes just a letter (usually the "O") — less distinctive in an app drawer
- Requires real type design skill to execute well; a bad custom wordmark looks worse than a good stock font
- May feel too "enterprise SaaS" if not done with the right energy
Where it shines: Marketing site, presentations, any context where the full name appears. Premium feel.
Where it might struggle: App icon at 44px. The extracted lettermark needs to carry enough personality on its own.
Direction 2: Abstract Progression Mark
Core idea: A geometric symbol that encodes the idea of forward motion, stacking, or upward trajectory. Paired with a clean wordmark (likely in Outfit).
Visual territory:
- Stacked shapes that grow or ascend — echoing the rank system's building metaphor (Open Road → Horizon)
- A series of bars, blocks, or segments that suggest both a chart going up and blocks being laid
- Negative space that reveals an arrow, path, or upward direction
How it connects: The gamification system is built on accumulation — days add up, XP compounds, ranks climb. An abstract mark that captures that kinetic feeling of things building on each other speaks directly to what the product does without being literal.
Strengths:
- Visually distinctive — abstract marks are harder to confuse with competitors
- Can be rendered in the brand gradient beautifully
- Works at small sizes if the geometry is simple enough
- Encodes the brand philosophy (every day adds up) in visual form
Risks:
- Abstract marks take longer to build recognition — users need repeated exposure
- If too abstract, it communicates nothing; if too literal (a bar chart), it looks like a finance app
- The meaning needs to be discoverable, not explained — if you have to tell people what it means, it's not working
Where it shines: App icon, social cards, merch, anywhere the mark stands alone.
Where it might struggle: If the geometry is too complex, it'll collapse at favicon size. Needs to be radically simple.
Direction 3: The Integrated "O"
Core idea: The letter "O" in "Objectuve" becomes the icon. It's designed with enough personality that it functions both as the first letter of the wordmark and as a standalone mark.
Visual territory:
- An "O" with an embedded element: a dot at center (bullseye/target), a break in the stroke (suggesting a path or entry point), internal geometry (a facet, a progress ring)
- The "O" could be a ring that's slightly incomplete — suggesting a journey in progress, not a closed loop
- Or a solid "O" with a gradient fill and a single distinctive detail (a notch, an inner ring, a subtle upward lean)
How it connects: "O" is for Objectuve. Simple. The letter is already the most iconic shape in the name. Designing it with purpose turns a functional lettermark into a meaningful symbol.
Strengths:
- Instantly recognizable as belonging to "Objectuve" — the connection is self-evident
- Works beautifully at app icon size (round shapes fit iOS squircles and Android circles naturally)
- Can carry the brand gradient
- Monogram approaches are having a strong moment in contemporary design (Arc, OpenAI, Threads)
Risks:
- "O" is the most common monogram letter — Google, Opera, Outlook, Overstock, etc.
- Must be distinctive enough that it doesn't disappear into a sea of circular app icons
- The internal detail is what makes or breaks it — needs to be simple enough for 16px, meaningful enough for 1024px
Where it shines: App icon, favicon, anywhere a compact mark is needed. The round form factor is native to mobile.
Where it might struggle: If underdifferentiated, it's just a circle. The detail inside the "O" is the entire design challenge.
Direction 4: The Momentum Arrow
Core idea: An arrow or directional element — not a literal arrow, but a shape that implies forward/upward movement. Paired with the wordmark.
Visual territory:
- A chevron, a swept angle, a tilted plane that suggests trajectory
- Could be integrated into a letterform (the "v" in "uve" naturally points upward)
- Or a standalone abstract arrow — simple, bold, unmistakable in direction
How it connects: Everything about Objectuve points forward: goals are future-oriented, streaks build momentum, ranks ascend. An arrow is the most universal symbol for "going somewhere." The anti-social philosophy also has a directional quality — do the thing, move on, keep going.
Strengths:
- Directional marks are viscerally energetic — they imply motion even when static
- Universal meaning: progress, growth, forward
- Can be extremely simple (good for small sizes)
- The upward angle naturally conveys optimism without being saccharine
Risks:
- Arrows are common — Nike, Deliveroo, countless fitness apps. Differentiation requires a fresh execution
- Can read as "shipping/logistics" if angled forward, or "finance" if angled up
- Risks feeling more like a generic startup mark than a distinctive brand if not carefully considered
Where it shines: App icon (arrows are crisp at small sizes), marketing hero (dynamic, energetic).
Where it might struggle: The arrow metaphor is so common that it needs a genuinely novel execution to feel owned.
Direction 5: The Achievement Mark
Core idea: A symbol that nods to the gamification system — badges, ranks, achievement. Not a literal badge shape, but something that evokes the feeling of earning, unlocking, or leveling up.
Visual territory:
- A faceted gem or crystalline shape (echoing badge rarity tiers)
- A shield or crest rendered in a modern, minimal way
- A shape with layers or segments that suggest tiers/levels
- A "burst" or radial element that suggests unlocking/achievement without being a star or trophy
How it connects: Gamification isn't a feature in Objectuve — it IS the product. Streaks, XP, badges, ranks are the core engagement loop. A mark that subtly encodes this identity makes the logo feel like it comes from the product rather than being applied to it.
Strengths:
- Deeply connected to what makes Objectuve distinctive (gamification isn't common in goal tracking)
- Rich visual vocabulary to draw from — gems, facets, layers, bursts
- Could evolve over time (the mark itself could have "rarity" variants for special contexts)
- Differentiates strongly from the clean, minimal logos common in the productivity space
Risks:
- Could read as "gaming" rather than "productivity with game mechanics" — wrong audience signal
- Faceted/crystalline shapes can feel trendy and date quickly
- If too decorative, it conflicts with the anti-social philosophy of restraint and clarity
- More complex shapes are harder to render at small sizes
Where it shines: Social cards, badge modals, achievement screens, merch — anywhere the brand's playful side leads.
Where it might struggle: Favicon if too detailed. Could feel incongruent in a B2B or Teams context if it leans too far into "game."
Competitive Landscape
Understanding what visual territory is already claimed helps identify where Objectuve can own space.
Habit/Goal Tracking Apps
| App | Visual Identity | Territory Claimed |
|---|---|---|
| Habitica | Pixel art, 8-bit retro RPG aesthetic. Green/purple palette. Character avatar as icon. | "Full RPG gamification" — deliberately niche, deliberately nerdy |
| Streaks | Minimal, solid color circles on black. Monochrome icon (white ring on blue). | "Apple-native minimalism" — ultra-clean, iOS design language |
| Strides | Green gradient, abstract upward bars/chart motif. | "Data-forward tracking" — analytical, chart-oriented |
| Way of Life | Colorful circles/dots, warm palette. Friendly, approachable. | "Casual, pattern-focused" — emphasis on visual trends |
| TickTick | Blue checkmark in a circle. Clean, corporate. | "Productivity tool" — task-management-first aesthetic |
| Reclaim.ai | Bold purple, abstract calendar/clock mark. | "AI-powered scheduling" — tech-forward, workspace tool |
| Fabulous | Warm, illustrated, artistic. Watercolor-inspired palette. | "Wellness/self-care" — soft, nurturing, magazine-quality |
What's Claimed
- Pixel art / retro: Habitica owns this completely
- Ultra-minimal circles: Streaks
- Chart/bar motifs: Strides, plus many generic fitness apps
- Warm/illustrated: Fabulous, and the broader wellness category
- Blue + checkmark: Saturated territory (TickTick, Todoist, Microsoft To Do)
Where Objectuve Can Differentiate
- Premium gamification that doesn't look like a game — the space between Habitica's 8-bit and Streaks' austerity is wide open. A mark that feels polished and modern but carries gamification DNA would be unique.
- The blue-cyan gradient — this specific gradient isn't strongly owned by anyone in the space. It reads as "tech-confident" without being cold.
- Typography-forward identity — most competitors lead with icons. A beautifully crafted wordmark would stand apart in app store listings where the name appears alongside the icon.
Key Decisions
Before any design work starts, these questions need answers. They're listed roughly in order of impact:
1. Icon-first or wordmark-first?
The app icon is arguably the most important surface — it's what users see dozens of times a day on their home screen. But the wordmark is what appears in marketing, App Store listings, headers, and anywhere the brand introduces itself.
If icon-first: The mark is designed to be excellent at 120x120, and the wordmark is built around it. The icon drives the identity.
If wordmark-first: The typography is designed first, and the icon is derived from it (usually a lettermark or extracted element). The name drives the identity.
A middle path: Design them simultaneously as a system, where neither dominates but both feel born from the same DNA.
2. How literal vs. how abstract?
A spectrum from "target with an arrow" (very literal) to "abstract geometric shape" (pure form). The further toward abstract, the more the mark ages well but the longer it takes to build recognition. The further toward literal, the faster it communicates but the more it risks becoming clip-art.
Recommendation to consider: Lean abstract, but with one design detail that becomes meaningful in context. Think of how Slack's hashtag evolved into their more abstract mark — still recognizable, but no longer a literal representation.
3. One logo or a system?
Options:
- Single lockup — icon + wordmark always appear together (simpler, but less flexible)
- Flexible system — icon, wordmark, and defined lockups (horizontal, stacked, icon-only). This is almost certainly the right answer for a product that spans mobile app icon, web header, marketing hero, and social cards.
4. Gradient, solid, or adaptive?
The blue-cyan gradient is the brand's most distinctive color element. But:
- Gradients can be harder to reproduce in some contexts (embroidery, single-color printing)
- A gradient-only logo needs solid-color and monochrome fallbacks
- Some surfaces (favicon at 16px) can't render gradients meaningfully
Likely answer: The primary version uses the gradient. Solid-color (primary blue #177bbb) and monochrome (black/white) variants are part of the system.
5. Does the mark reference gamification?
This is a philosophical question. Gamification is the product's core identity — but the logo also needs to work in "serious" contexts (Teams tier, B2B partnerships, press). A mark that subtly encodes progression or achievement can do both. A mark that looks like a game badge might not.
Practical Constraints
Size Requirements
| Context | Size | Implication |
|---|---|---|
| Favicon | 16x16, 32x32 | Must be recognizable with ~4 distinguishable shapes max |
| iOS notification | 44x44 pt | Needs to read instantly in a glance |
| App icon (home screen) | 120x120 pt (rendered at 2-3x) | The money shot — this is the logo's primary habitat |
| App Store/Play Store | 1024x1024 | Full detail version, often shown alongside the name |
| Web header | ~170x34 (current) | Horizontal lockup, wordmark-forward |
| Marketing hero | Full-width | Maximum visual impact, gradient shines here |
| Social/OG card | 1200x630 | Brand stamp on shared content |
Platform-Specific Requirements
iOS: Single 1024x1024 PNG, auto-masked to squircle. No transparency. Must look good in squircle crop.
Android: Adaptive icon system — foreground layer (icon) + background layer (color/gradient). System applies various mask shapes (circle, squircle, teardrop, etc.). The icon must have padding (safe zone) and look good under all masks.
PWA: Multiple sizes needed (72, 96, 128, 192, 256, 384, 512). Maskable icon variant recommended.
Format Requirements
- SVG source is non-negotiable (the PNG-only situation is the root problem)
- SVG for web/marketing, PNG exports at required sizes for native
- Consider a single SVG that gracefully degrades: the full lockup can be cropped to icon-only at small sizes
- Font embedded or converted to paths (no external font dependencies in the SVG)
Dark/Light Mode
Both are first-class in the app. The logo needs intentional variants:
- Light background: Full-color mark + dark or gradient wordmark
- Dark background: Full-color mark + white or light wordmark
- Monochrome: Single-color version for constrained contexts
Currently, dark mode is handled by swapping between two separate PNGs. The new system should define this properly.
Recommended Next Steps
1. Make the Key Decisions First
Before touching any design tool, resolve the five decisions above. They constrain the design space dramatically — there's no point exploring a detailed gamification badge mark if the decision is "wordmark-first, abstract."
A useful exercise: rank the five decisions, discuss each for 10 minutes, and commit. Write the answers down. They become the filter for evaluating concepts.
2. Explore 2-3 Directions, Not 5
Five directions is good for thinking. For actual design exploration, narrow to 2-3 based on the decisions above. Each direction should be explored at three scales simultaneously: app icon (120px), horizontal lockup (header), and favicon (32px). If a concept doesn't work at all three, it's out.
3. Execution Options
| Approach | Pros | Cons |
|---|---|---|
| Professional designer | Highest quality, outside perspective, polished deliverables | Cost, timeline, back-and-forth cycles |
| Design tool (Figma/Illustrator) | Full control, iterate quickly, no coordination overhead | Requires design skill, risk of "good enough" trap |
| AI-assisted exploration + refinement | Rapid concept generation, useful for exploring territory | Output needs significant refinement, can feel generic |
| Type foundry / custom lettering | Premium wordmark, truly unique | Expensive, long timeline, narrow scope (wordmark only) |
A pragmatic path: Use AI tools or rough sketches to rapidly explore the territory. Identify which direction resonates. Then either refine internally in Figma or engage a designer for the final execution. The exploration phase should be cheap and fast; the execution phase is where quality matters.
4. Phased Rollout
Don't try to update everything at once. A suggested order:
Phase 1 — Core identity (before launch)
- Final SVG mark + wordmark + lockups
- App icon (iOS + Android)
- Favicon set (16, 32, 180, 192, 512)
- Marketing site header + footer
Phase 2 — Full integration (launch week)
- In-app header and side navigation
- Sign-in / sign-up screens
- OG/social card template
- PWA manifest icons
Phase 3 — Extended surfaces (post-launch)
- Documentation site
- Storybook / design system
- Email templates
- Print / presentation templates
5. What to Preserve
Not everything needs to change:
- The name — "Objectuve" is strong. Keep it.
- The color system — the gradient, the palette, the dark/light modes. These are working.
- The typography — Outfit for headlines, Inter for body. Consistent and modern.
- The tone — the logo should feel like the same brand, evolved, not a rebrand.
The logo refresh is about alignment, not reinvention. The product has outgrown the mark. The mark needs to catch up to where everything else already is.
This document is a starting point for discussion, not a final direction. The best logo will come from narrowing these possibilities through conversation, iteration, and honest evaluation.
Last updated: 2026-09-11 (v4.8.3) — footer currency fix + clarified the deleted assets/legacy/ citation as pre-V11 history (OBJ-3649); still a verified historical exploration document (March 2026)