Brand guide
How to use the Mapiddiction brand.
Everything needed to make something that looks and sounds like Mapiddiction: on the web, in the builder, on the maps themselves, and beside our clients’ brands.
Foundations
Using this guide
The short answer to “what does Mapiddiction look and sound like?”. Written so you can act on it without asking anyone, and honest about what is not decided yet.
This guide is for everyone who makes something with the Mapiddiction name on it: the Mobiddiction team who build the platform and produce client maps, the people who write the website and the knowledge base, and the designers, illustrators and printers who work on map projects. Nothing in it is confidential. You can send the whole file to a supplier.
Mapiddiction is a product of Mobiddiction. Everything here sits inside the Mobiddiction brand guide (v1.6). Where this guide is silent, the master guide applies. Where they disagree, the master guide wins and this guide is wrong: tell us.
What is binding, and what is not
Everything in a red Don’t panel is binding. The rest is a strong default. Items marked Pending approval are recommendations written for this guide that nobody has signed off yet. Items marked TBC are facts we do not have. Use both with care, and never quote them as settled.
✓ Do
- Start from the master files listed in Section 18.
- Check which layer you are working on (Section 03) before you open a design tool.
- Send this guide to a supplier before they start work.
- Ask when something isn’t covered. Don’t guess.
× Don’t
- Copy colours or logos out of an old file, a screenshot or the website. Use the masters.
- Use Mobiconnect logos or colours for Mapiddiction. Mobiconnect is a separate brand.
- Treat something as allowed just because it isn’t explicitly banned.
- Redraw, trace or rebuild any part of the logo.
Who owns what
- Brand owner
- Mobiddiction Pty Ltd. Mapiddiction is a Mobiddiction product, built and run on the M4 platform.
- Guide & masters
- Maintained by Mobiddiction. The product owner for brand decisions is TBC.
- Requests
- Files, questions and change requests: contactus@mobiddiction.com.au
Clear space and minimum sizes (Section 05) · a text-safe secondary grey (Section 07) · the map grid device (Section 09) · the house tagline form and “AI wayfinding” spelling (Section 03) · the Mapiddiction demo marker set and route colour (Sections 13 and 14) · attribution on client maps (Section 17) · renamed and outlined logo masters (Section 18).
How to print it
Export from your browser at A4, default margins, background graphics on. If background graphics are off, every swatch prints white. Sections start on a new page by design.
Requesting a change: email the section number, what you tried to do, and what got in the way. Changes are made once, here, and the version number on the cover moves.
Mapiddiction at a glance
The facts that must be right every time, the whole identity on one page, and descriptions you can use without rewriting.
- Name
- Mapiddiction
- What it is
- A map-building platform for custom interactive maps with AI wayfinding
- Owned by
- Mobiddiction, as a product on its M4 platform
- Surfaces
- Marketing site mapiddiction.com · web app (builder and workspace) at app.mapiddiction.com · public map viewer and embeds · knowledge base
- Built for
- Retail, healthcare, education and enterprise. In practice: show grounds, events, campuses, memorial parks, shopping centres and hospitals.
- Map types
- Image, Standard, Overlay and Builder (Section 12)
The identity on one page
Poppins
Bold · SemiBold · Medium · Regular · Light
The facet colours of the mark. They belong to the logo artwork, not to layouts (Section 07).
Descriptions in use
These come from the live site. They are the best wording we have, but none has been formally approved Pending approval. Trim from the end; never rewrite from the middle. Check feature lists against the current release notes before you print them.
Custom maps with AI powered wayfinding.
Mapiddiction empowers businesses to create and manage interactive maps. Built for retail, healthcare, education, and enterprise.
Mapiddiction is Mobiddiction’s platform for custom interactive maps. Create Image, Standard or Overlay maps, add points of interest, labels and info windows, and turn on wayfinding so visitors get turn-by-turn directions. Share a link, embed the map on your site or use QR codes, manage every map from one workspace, and see how visitors use them in Analytics.
Architecture & naming
Mapiddiction sits on the product layer of the Mobiddiction brand. Knowing that decides whose logo leads, which colours apply and where the credit goes.
| Layer | Here | What it means for Mapiddiction |
|---|---|---|
| Master brand | Mobiddiction | Our parent. Its typography, spacing, shape and voice rules carry through. It appears once per surface as “Powered by Mobiddiction”. |
| Platform | M4 | The platform Mapiddiction runs on. A name in running text only: no logo, colour or typeface. Never “Mapiddiction M4”. |
| Product | Mapiddiction | Holds its own name, mark and accent colours. Must stay legibly related to Mobiddiction and must carry attribution. |
| Client programs | Client maps | Maps we build for a client, under the client’s brand. The client’s brand governs. We appear only in the attribution position, if at all (Section 17). |
Writing the name
| Write | Never |
|---|---|
| Mapiddiction | MapIddiction · Map-iddiction · Mapaddiction · MAPIDDICTION (in running text) · Mapiddiction™ |
| Mapiddiction’s builder | A plural or a verb: “Mapiddictions”, “mapiddict it” |
| Image map, Standard map, Overlay map, Builder | “Google map” for a Standard map (its legacy name) · IMAGE MAP in capitals |
| AI wayfinding in body copy Pending approval | WayFinding · Way-finding · AI-Wayfinding as a product name |
| point of interest (POI) on first use, then POI | “pin” and “marker” mixed in the same piece. Use “marker” for the symbol on the map, “POI” for the place. |
| Mobiddiction, M4, Mobiconnect as the master guide writes them | MobiConnect · Mobiconnect as Mapiddiction’s old name in customer copy |
- The wordmark sets the name in widely spaced capitals. That spacing belongs to the logo only. Don’t imitate it in headings or text.
- The site currently writes the tagline “Custom Maps with AI powered WayFinding”. The house form proposed here is sentence case: “Custom maps with AI powered wayfinding” Pending approval.
- No ™ or ® on Mapiddiction unless legal confirms a registration for that exact mark. Registration status is TBC.
Identity
Logo
A faceted, folded “M” that reads as a folded paper map. It works on its own as the app icon and avatar, and pairs with the MAPIDDICTION wordmark in two lockups.
The system
Every version is built from two parts. The mark is a fold of triangular facets: yellow, orange and red across the top, blue, light blue and cyan across the lower left, a magenta facet on the right, and charcoal fold shadows that give it depth. The wordmark is MAPIDDICTION in Poppins Regular capitals, tracked wide. It is part of the artwork and is never retyped.
Inline · defaultHeaders, the web app, email, documents, footers.
StackedSquare and portrait spaces: covers, posters, social tiles, splash screens.
MarkApp icon, favicon, social avatar, and small spaces where the name is already nearby.
Two colourways
The mark is always full colour. Only the wordmark changes, and it changes with the background. The file names describe the mode they were made for, which trips people up: the dark files are for light backgrounds, the light files for dark ones.
Charcoal wordmark · files named “dark”Wordmark #323232. For white, Canvas, Sky and the pastel tints. The website uses it in light mode.
White wordmark · files named “light”Wordmark white. For Night, Footer and dark photographs. The website uses it in dark mode.
| Background | Use | Never |
|---|---|---|
| White, Canvas, Sky, tints | Charcoal wordmark | White wordmark (it disappears) |
| Night, Footer, dark UI | White wordmark | Charcoal wordmark |
| Map Blue, Facet Magenta | Avoid. If unavoidable, white wordmark, and check the mark’s blue and magenta facets still separate from the ground. | A logo on a full-bleed brand-colour block as a default layout |
| Photographs and busy maps | On a calm area, or on a white or Night panel | Directly over map detail or markers |
There is no mono black or mono white version of the mark. Until one is drawn and approved, one-colour jobs (embroidery, etching, single-colour print) need a request (Section 18). Don’t make your own by filling the artwork.
Clear space & size
Give the logo room, and stop shrinking before the spaced capitals stop being readable.
The values on this page are this guide’s recommendations, based on the artwork and on the rule of thumb in the existing notes (“about the height of one facet”). They are not yet signed off.
Clear space
Define x as the height of one facet, about a quarter of the lockup’s height. Keep at least x clear on all four sides of either lockup and of the mark. Nothing goes in that space: no text, rules, other logos, map detail, markers or page edge.
The files carry a little built-in margin. Measure clear space from the artwork, not the file edge. On a crowded layout, make the logo smaller rather than squeezing the space.
Minimum size
| Version | Screen (artwork width) | Print (artwork width) |
|---|---|---|
| Inline lockup | 140 px | 35 mm |
| Stacked lockup | 80 px | 22 mm |
| Mark | 24 px (16 px as a favicon only) | 8 mm |
Below these sizes the spaced wordmark turns into a grey line. Use the next version down: inline, then stacked, then the mark on its own.
At minimum size, shown at actual screen size
Logo misuse
The mistakes that happen most often. Each one is a defect, not a matter of taste.
Don’t stretch or squash. Scale it proportionally.
Don’t recolour the facets, even with palette colours.
Don’t flatten or desaturate the mark.
Don’t rotate or tilt it.
Don’t add effects: shadows, glows, outlines, bevels.
Don’t retype the wordmark or swap the font.
Don’t use the white wordmark on a light background.
Don’t place it over map detail. Give it a calm panel.
✓ Do
- Scale proportionally, from a master file.
- Pick the wordmark colour that suits the background (Section 04).
- Switch to the mark alone rather than going under a minimum size.
× Don’t
- Change the gap or proportion between the mark and the wordmark.
- Pull facets out of the mark to use as loose decoration.
- Put the logo in a box, badge or frame it didn’t come with.
- Add a tagline, “Maps” or “by Mobiddiction” to a lockup.
- Use the mark as a map marker or route icon.
Colour
A confident blue and a magenta accent, both taken from the mark, on white and soft neutrals. Every swatch shows its contrast against white, and that ratio decides what the colour is allowed to do.
Values come from the site’s theme tokens (material-custom.scss). Swatch names are this guide’s labels for those tokens.
Brand colours
Map Blue
#5C8BE7 · --primary
RGB 92 139 231
The brand colour. Buttons, highlights, active states, routes and charts. Text on it is Text #202020 (4.89:1). White on it is for large text only.
Facet Magenta
#C10D68 · --accent
RGB 193 13 104
The magenta facet. Links, eyebrows, the one highlighted word in a headline. Use sparingly beside Map Blue.
Text
#202020 · --primary-text
RGB 32 32 32
Body text and headings on light surfaces. Use this instead of pure black.
Night
#0F172A · dark hero
RGB 15 23 42
Dark heroes, covers and part dividers. Carries the white wordmark.
Neutrals
Dark Grey
#232821 · --dark-grey
Strong UI text and icons. Also Mobiddiction’s Ink.
Footer
#1E1E1E · --footer-bg
Site footer and dark bands. Always with the white Mobiddiction logo.
Med Grey
#8B8B8E · --med-grey
Icons, disabled states, map furniture. Too light for text on white.
Light Grey
#D4D1CF · --light-grey
Dividers, borders and table rules.
Canvas
#F7F7FF · --section-soft-purple
Page and section grounds behind white cards.
Fold Grey Pending
#5B5957 · from the logo
Proposed secondary text colour for captions and metadata, because Med Grey fails. Not yet a site token.
Tints and labels
The four pastel tints are marked “legacy” in the code. Use them for soft section and card grounds with Text on top (all over 12:1). Don’t add new ones.
Status
Success (2.69:1) and Warning (2.16:1) are fills and icons only, with Text on top. Error is text safe (7.33:1).
Proportion
Mapiddiction is bright and open. White and Canvas do most of the work, so the maps themselves carry the colour. Map Blue leads, Night anchors, and Facet Magenta is a highlight rather than a flood.
Approximate share of a typical layout. Facet Magenta (last) stays around 5%.
Dark mode
The site and app have a dark theme. Its tokens are lighter so they read on dark surfaces: primary #7BA3F7 (7.16:1 on Night), accent #E91E8C, surfaces stepping from #121212. Use them only inside the dark theme. Full list in Appendix A.
Artwork-only tones
These are the gradient stops inside the mark. They are listed so artwork can be matched, not for use in layouts, charts or markers.
✓ Do
- Put Text
#202020on Map Blue buttons and chips, or keep white text 18.5 px bold and larger. - Use Facet Magenta for links and small accent text on white.
- Use the status colours for success, warnings and errors.
× Don’t
- Set body-size white text on Map Blue (3.33:1).
- Set text in Med Grey on white.
- Use the facet gradient as a background, or rebuild it as a rainbow.
- Hard-code colours outside these tokens, or restyle Angular Material components with custom colours. Use the theme variables.
Several site buttons set white text on Map Blue at body size, which is below WCAG AA. Fixing it means Text on Map Blue, a larger bold label, or a deeper blue token. Which one is TBC.
No CMYK or Pantone values have been defined TBC. Until they are, print jobs convert from the screen values and must be proofed. Add matched values here when a job sets them.
Typography
One family, Poppins: the same typeface as the Mobiddiction master brand. Geometric, wide-apertured and clear at small sizes, which matters on a map.
Aa
Poppins
ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz 0123456789 & % / : – “”
Type scale
The scale is the master brand’s. A product keeps our typography and doesn’t invent its own.
| Style | Size / line height | Sample |
|---|---|---|
| Display | 56–72 / 1.05 · 700 · −2.5% | Custom maps, made easy |
| Heading | 32–40 / 1.15 · 700 · −2% | Three map types |
| Subheading | 20–24 / 1.3 · 600 | Rich POIs and info windows |
| Body | 16–18 / 1.6 · 400 | Add points of interest, labels and info windows, then publish. |
| Small | 14 / 1.55 · 400 | Updated 26 October 2026 |
| Eyebrow | 12 · 600 · caps +25% | Map solution |
- Headings in sentence case, buttons and navigation in Title Case, as the master guide sets out.
- Never use weight 800 or 900, and never italic for emphasis. Use weight or colour.
- UI icons on the site and in the builder use Google’s Material icon fonts, not a second typeface.
Type on maps
Marker labels default to 14 px at weight 400, with an optional white outline or soft shadow so they read over any basemap (Section 13). On client maps, the client’s own typeface can replace Poppins for labels and legends. Melbourne Royal Show, for example, uses Fann Grotesque Pro. Mapiddiction’s own interface around the map stays in Poppins.
Fallbacks
| Where | Use |
|---|---|
| Web, app, design tools | Poppins 300–700 (Google Fonts, SIL Open Font License), falling back to Segoe UI and system sans |
| Word, PowerPoint, Outlook | Poppins where installed, otherwise Arial |
| The master guide’s system stack. Email is the one exception to Poppins. |
The map grid
Contour lines, a street grid, one route and a few markers. It is the graphic device that tells people they are looking at Mapiddiction before they read the name.
The map grid is drawn for this guide, from the stylised route-and-markers illustration in the site’s hero. It is a proposal until approved.
On NightBlue contours, a faint street grid, a Map Blue route. For covers, heroes and social.
On SkyThe same drawing, quieter. For documents, slides and email footers.
The parts
| Part | Rule |
|---|---|
| Contours | Thin, smooth, closed lines in Map Blue or Dark Mode Blue at low opacity. Never filled, never shaded like real terrain. |
| Street grid | A faint square grid plus a few wide, rounded “streets”. Background only. |
| Route | One continuous Map Blue line from a blue start dot to one destination marker. Never more than one route. |
| Markers | Circle markers with white borders, in the facet colours, as in Section 13. Five at most, and the destination is the only teardrop. |
✓ Do
- Run it along the bottom or one side of a layout, bleeding off the edge.
- Keep text and logos on the calm area above it.
- Redraw the route to suit the layout. The rules stay the same.
× Don’t
- Use it on a client’s map or inside the public viewer. It is Mapiddiction’s, not the client’s.
- Put the Mapiddiction mark on the route or as a marker.
- Use real place names, real streets or a real client site in the device.
- Animate it as a loop. A single route draw on load is fine.
Imagery
The best picture of Mapiddiction is a real map we made. Illustrated client maps first, the builder second, photography third.
What to show
- Real client maps, with written permission, at a size where the detail reads. Both maps above are in the public gallery on the site.
- The builder and viewer as clean screenshots: current version, realistic data, nothing personal.
- Photography of places (venues, shops, gardens), as used inside info windows. Natural light, honest colour, no tinting to the palette.
✓ Do
- Crop to a part of the map that tells a story: an entrance, a route, a busy area.
- Write alt text that says what the map shows, not what the section is about.
- Keep the permission with the asset.
× Don’t
- Show a competitor’s product, or our map styled to look like one.
- Show restricted or sensitive areas of hospitals, schools or cemeteries. The policy for these sites is TBC, so ask first.
- Show real visitor locations, routes or heatmaps that could identify a person.
- Use collages, tinted photographs or generic stock maps.
Voice
Voice & tone
Friendly, confident and plain-English. Mapiddiction is allowed a little more energy than its parent, but never at the cost of the master brand’s rules.
How Mapiddiction sounds
Say what the visitor or the venue gets: “Visitors get turn-by-turn directions”, not “the routing engine computes paths”.
Explain map types in one line each: “Image is your design only. Standard is a base map with POIs. Overlay is your design on a base map.”
One energetic line in a hero is fine. No exclamation marks, no stacked superlatives, no “revolutionary” claims we can’t show.
Australian spelling (customise, organisation, digitise, colour) and prices in AUD first.
| Instead of (live site today) | Write |
|---|---|
| Digitise your maps with over 50+ features | Digitise your maps with more than 50 features |
| *Get started for free. No CC Required. | Start free. No credit card needed. |
| READY TO REVOLUTIONISE YOUR MAPPING EXPERIENCE? | Ready to build your first map? |
| Custom Maps with AI powered WayFinding | Custom maps with AI powered wayfinding Pending approval |
Copy on the map
- POI names are the client’s proper names, written the way the client writes them: “Grand Pavilion”, “Garden of Peace”.
- Directions use landmarks and metres: “Turn left at the Grand Pavilion. 120 m to Gate 4.” Metric units with a space.
- Accessibility is stated, not implied: “Step-free route via the lift”.
- Labels in the builder follow the master rules: sentence case, four words at most, no trailing colon, none of our internal vocabulary (no slugs, keys, IDs or enum values on screen).
- Dates as 26 October 2026; times as 9:30 am. No em dashes. An en dash for ranges only.
Don’t write your own security or certification wording. Use the master guide’s approved sentence. Location data is sensitive: describe analytics as aggregated and kept for 90 days, never as tracking individuals.
Applying it
Map styles & basemaps
The basemap is the stage, not the show. Pick the quietest style that still tells people where they are, and let the client’s content carry the colour.
Four map types
| Type | Base | Choose it when |
|---|---|---|
| Image | Your design only, one image per level | The site isn’t on a street map, or it’s indoors. No blue dot. |
| Standard | A basemap with POIs | The street network is the context: precincts, festivals across a city. |
| Overlay | Your design aligned on a basemap | An illustrated map that also needs the blue dot and real-world position. |
| Builder | Vector plans drawn in the platform | Floor plans you draw rather than illustrate. |
The basemap styles
Since 2026, Standard and Overlay maps use these six styles. The older CARTO and Stadia styles are retired. Don’t show them in new material.
Light
ofm-positron · vector
Default choice under colourful overlays and markers.
Muted
ofm-fiord · vector
Lower contrast again. For dense marker sets.
Dark
ofm-dark · vector
Dark theme, screens in dim venues, night events.
Streets
ofm-bright · vector
When street names and transport matter to the visitor.
Detailed
ofm-liberty · vector
Maximum context. Use sparingly with many markers.
Satellite
esri-satellite · raster
Outdoor sites, and aligning overlays to the ground.
Previews are the picker thumbnails. Muted and Detailed reuse the nearest existing preview until their own are made. Five styles come from OpenFreeMap (OpenMapTiles, OpenStreetMap data); Satellite comes from Esri.
✓ Do
- Start with Light. Move to Streets or Satellite only when the visitor needs that context.
- Match the basemap to the theme: Dark style in dark mode.
- Check markers and labels on the chosen style at the smallest zoom you allow.
× Don’t
- Remove, cover or shrink the provider attribution. It is a licence condition.
- Screenshot a basemap and use it as a client’s illustrated map.
- Recolour tiles to brand colours.
Pins & POI icons
Markers are built from marker types: one reusable design per category, with its own icon, colours and size. Get the type right and every POI on the map follows.
Five marker styles
Drawn to the product’s own rules: the teardrop is a circle with one square corner, turned 45°; the square point carries a white pointer; a white border on every style except Icon only.
Sizes
| Size | Marker | Icon inside | Icon only | White border |
|---|---|---|---|---|
| Small | 24 × 24 px | 14 px | 24 px | 2 px |
| Medium (default) | 32 × 32 px | 18 px | 32 px | 3 px |
| Large | 40 × 40 px | 22 px | 40 px | 4 px |
Colour roles
Every marker type has four colours, plus their reversed pair for dark basemaps and dark mode.
| Role | Rule |
|---|---|
| Default colour | The category’s colour. One colour per marker type, kept consistent with the legend. |
| Selection colour | Must differ clearly from every default colour on the same map, so the chosen POI is obvious. |
| Icon colour | At least 3:1 against the marker fill (WCAG non-text contrast). White on Map Blue is 3.33:1; Text on a pastel marker is over 10:1. |
| Reverse colours | Used on dark basemaps and in dark mode. Set them; don’t leave them blank and hope. |
Whose colours
On client maps, marker colours belong to the client’s legend, not to Mapiddiction. The builder offers palette groups (pastel, vibrant, earthy, monochromatic, neutral cool) as starting points. The product default, a blue #3B82F6 with white icons, is a fallback, not a brand colour.
On Mapiddiction’s own demo maps, screenshots and marketing, use Map Blue markers with white icons and Facet Magenta for the selected state, as shown above Pending approval.
Icons and labels
- Icon sources: Material Symbols, Font Awesome (solid), or a client icon uploaded to M4 Media. One library per map. Don’t mix line and solid icons.
- Uploaded icons: square, transparent background, a single colour, readable at 14 px. SVG or PNG at 2×.
- Legend codes: a marker type can show a code instead of an icon, such as F-1 or B-9 (Section 14).
- Labels: 14 px by default, 8 px from the marker, with a white outline or soft shadow over busy maps. Hide labels below a sensible zoom rather than letting them collide.
✓ Do
- Create one marker type per category before placing POIs.
- Use the same shape for every marker on a map, unless shape itself carries meaning.
- Keep the white border on: it separates markers from any basemap.
× Don’t
- Rely on colour alone. Pair it with an icon, a code or a label.
- Use the facet gradient or the Mapiddiction mark as a marker.
- Give two categories the same colour, or the selection colour to a category.
Wayfinding & legends
A visitor should know where they are, where they’re going and how to get there in one glance. Routes, levels and legends all serve that glance.
Legend
Facilities
- F-1Administration office
- F-2Chapel
Burial
- B-1Lawn cemetery
Cremation gardens
- C-1Garden of Peace
Colours from the Centenary Memorial Gardens legend. A client’s palette, not ours.
Routes
| Element | Rule |
|---|---|
| Start | The blue dot: the visitor’s live position on geo-enabled maps (Standard and Overlay), or a chosen start POI. Image maps have no blue dot, so start from a POI or a QR code. |
| Route line | One continuous line, thick enough to read over the basemap, in a colour no marker type uses. On Mapiddiction’s own demos, Map Blue Pending approval. The public viewer’s route styling is TBC. |
| Destination | The destination POI’s own marker, in its selected state. |
| Changing level | Stairs, lifts, escalators and ramps join levels. Name the connector in the step: “Take the lift to Level 2”. |
| Accessible routes | Offer the step-free option wherever routes are tagged. Say it in words, not just with an icon. |
Legends
- Group by marker type, in a fixed legend order, with a title per group.
- Give each group a one-letter prefix and number its entries: F for Facilities gives F-1, F-2. The same codes appear on the markers, on the illustrated map and in print.
- Legend swatches match the marker exactly: same colour, same shape.
- In print, the automated legend sets 16 pt swatches, 11 pt entries and a 14 pt title. Keep those proportions when you lay one out by hand.
✓ Do
- Put entrances, toilets, first aid and accessible routes in every legend where they exist.
- Keep north up unless the site has a strong reason, and show a north arrow when you rotate.
- Offer QR codes into wayfinding at physical entrances.
× Don’t
- Draw more than one route at a time.
- Use red for a route. It reads as closed or danger.
- Show restricted areas, staff-only routes or security points on a public map.
Illustrated maps
The bespoke illustrated map is Mapiddiction’s signature. These are the standards every one is produced to, from site data to published overlay.
- Gather site dataSite plans, PDFs, satellite or drone imagery. For overlays, georeference it (for example in QGIS, keeping the
.pgwworld file). - IllustrateIn Adobe Illustrator, one
.aimaster per client, in Drafts, WIP and Final folders. - Place markersOptionally with the MarkerAutomation script, from the map’s legend data. The Advanced version also builds the legend.
- ExportWebP at 1×, 2× and 4× for the web. A3 PDF or EPS for print.
- Upload & alignAs an Overlay with two image points and two map points, or as an Image map with one image per level.
- Load & publishBulk-load POIs and content, check every marker against the legend, then publish under a licence.
Drawing standards
| Topic | Standard |
|---|---|
| Style | Flat or isometric, colourful and detailed: buildings, trees, paths, water, parking. The client’s site should be recognisable to someone standing in it. |
| Colour | The client’s palette and the site’s real character: green for lawns and gardens, grey for roads and parking, blue for water. Not Mapiddiction’s brand colours. |
| Type | Road and area names only, in the client’s typeface or Poppins. POI names belong to markers, not the artwork, so they can be updated without a redraw. |
| Markers | Interactive maps: leave markers out of the artwork; the platform draws them. Print maps: place them with the script. Defaults: 24 pt circles, 1.5 pt white stroke, 10 pt codes. |
| Calibration | Calibration crosses (magenta, 1.25 pt) live on their own layer and are hidden before export. |
| Export | Export every size from the same artboard so overlay alignment carries over. Large images are tiled automatically on upload. |
| Versions | A new season or year is a new version of the master, not a new file from scratch. Keep the previous year’s master. |
✓ Do
- Proof the 1× export on a phone before upload. If a path or label can’t be read there, simplify.
- Record the source of every satellite or drone image used as a base.
× Don’t
- Trace copyrighted maps or another supplier’s artwork.
- Put the Mapiddiction logo or the map grid device inside a client’s illustration.
- Bake text into the artwork that the client will need to change.
Web, app & embeds
The places people meet Mapiddiction. The brand leads on our own surfaces and steps back on the map.
Map solution
Custom maps with AI powered wayfinding
Embed your custom map across websites, digital screens and mobile apps.
Get StartedMarketing site, light mode. Charcoal-wordmark inline lockup in the header, linking home.
| Surface | Rule |
|---|---|
| Marketing site | Theme-aware logo: charcoal wordmark in light mode, white in dark mode. Dark footer with “Powered by” and the white Mobiddiction logo, always. Favicon: the mark. |
| Web app | Builder and workspace run on M4. Use theme variables. Don’t restyle Angular Material components. |
| Public viewer | The map fills the frame. The client’s content leads. Mapiddiction attribution follows Section 17. |
| Embeds | Choose the profile by frame size: pins for about 300×200, tooltips for about 600×400, full for the whole viewer. ui=auto upgrades when the frame grows. |
| QR codes | Dark on white with a quiet zone of at least four modules, and a call to action beside it: “Scan for directions”. Never put the logo inside the code. |
| Follows the master guide’s email rules, with the “Powered by Mobiddiction” attribution in the footer. |
Interface colour
- Primary buttons: Map Blue with Text
#202020labels (4.89:1), as recommended in Section 07. - Links: Facet Magenta, underlined in running text.
- Focus rings: 3 px Night, offset 3 px. Map Blue alone is too light to mark focus on white.
- Radius and spacing: the site tokens (radius 5, 10, 20 and 30 px; spacing 4 to 48 px; page width 1200 px). Full list in Appendix A.
- Accessibility: the stated target for the builder and public maps is WCAG 2.2 AA.
Client maps & co-branding
Most Mapiddiction maps carry someone else’s name. Who leads depends on whose surface it is, and the credit appears once.
| Surface | Who leads | Attribution |
|---|---|---|
| Mapiddiction’s own: site, app, emails, social, decks | Mapiddiction | “Powered by Mobiddiction” once, in the footer or on the about page. White Mobiddiction logo on dark footers. |
| A client map: public viewer, embed, kiosk | The client | At most one small “Powered by Mapiddiction” credit Pending approval. The viewer shows none today. Whether it appears is set per agreement. |
| A client’s printed map | The client | None by default. Only if the client agrees in writing. |
| Case studies and the gallery | Mapiddiction | Client logos and maps with written permission, labelled as a client list, not an endorsement. |
Client map in the public viewerThe client’s logo, colours and markers. A small credit in the corner, away from map attribution, if agreed.
Mapiddiction site footerAs built: “Powered by” and the white Mobiddiction logo, linking to mobiddiction.com.au.
✓ Do
- Let a white-labelled client map replace our colours and logo completely.
- Get the client’s logo file from the client, with written permission, and follow their guide for it.
- Describe the relationship accurately: “a map for”, “delivered for”.
× Don’t
- Show both “Powered by Mapiddiction” and “Powered by Mobiddiction” on the same surface.
- Put the Mobiddiction mark inside a client map beyond the attribution position.
- Build a combined lockup of Mapiddiction and a client logo.
- Keep a former client in the gallery or a logo strip past the agreement.
- Put a government crest on anything without explicit written approval.
Files & requests
Always start from a master. If the file you need isn’t listed, ask for it rather than making it.
The logo files
| File | Formats | Use |
|---|---|---|
mapiddiction-inline-dark | SVG · WebP 4× | Inline lockup, charcoal wordmark, for light backgrounds |
mapiddiction-inline-light | SVG · WebP 4× | Inline lockup, white wordmark, for dark backgrounds |
mapiddiction-stacked-dark / -light | SVG · WebP 4× | Stacked lockup, as above |
mapiddiction-icon | WebP 1362 / 500 · PNG 302 | The mark: app icon, favicon, social avatar |
Mapiddiction-inline-white | PNG 1000 | Legacy white-wordmark lockup. Use the SVG instead. |
mobiddiction-logo-inline-white / -mobiRed | WebP | Parent logo for the “Powered by” credit. Prefer the master guide’s files. |
In the current SVG files the wordmark is live Poppins text, not outlines. Without Poppins installed it falls back to another font. Outline it, or use the WebP or a PDF export. Outlined masters are Pending approval.
| Item | Status |
|---|---|
Original logo master (.ai) | TBC where it is held |
| Mono black and mono white versions | Not drawn Pending approval |
File names to the master pattern, e.g. mapiddiction-logo-inline-dark.svg | Pending approval |
| CMYK and Pantone values | TBC |
Where things live
- Logo pack
- The Mapiddiction project pack,
assets/logos/. Code masters in the marketing site repo,src/assets/logos/. - Client masters
- Each client’s folder in the Mapiddiction work drive:
.ai,.psd, TIFF and exports in Drafts, WIP and Final. - Map gallery
- The marketing site repo,
src/assets/map-gallery/. - Marker automation
- The
illustrator-manualfolder: scripts plus the quick and technical references.
Requests
Email contactus@mobiddiction.com.au with what you are making, where it will appear, the size, and your deadline. Client logos and maps need the client’s written permission first.
Appendices
Colour tokens
The values the marketing site uses today, from src/themes/material-custom.scss, plus the marker defaults from the builder.
/* Brand, shared */
:root {
--primary-color: #5c8be7; /* Map Blue, fills, large text */
--secondary-color: #c10d68; /* Facet Magenta, text safe */
--success-color: #00b389; /* fills and icons only */
--warn-color: #ff9800; /* fills and icons only */
--error-color: #b00020; /* text safe */
--info-color: #5c8be7;
--dark-grey: #232821; --med-grey: #8b8b8e; --light-grey: #d4d1cf;
--extra-color: #e5eeff; --extra-color-2: #ffd6ea; /* legacy tints */
--extra-color-3: #ebffda; --extra-color-4: #fff9ad;
--font-family-primary: 'Poppins', sans-serif;
--border-radius-sm: 5px; --border-radius-md: 10px;
--border-radius-lg: 20px; --border-radius-xl: 30px;
--spacing-xs: 4px; --spacing-sm: 8px; --spacing-md: 16px;
--spacing-lg: 24px; --spacing-xl: 32px; --spacing-2xl: 48px;
--page-width: 1200px;
}
/* Light mode (default) */
--primary-text: #202020; --primary: #5c8be7; --accent: #c10d68;
--footer-bg: #1e1e1e; --section-hero-bg: #eafaff; --section-soft-purple: #f7f7ff;
--section-label-gold: #ffc843; --section-label-orange: #ffa033;
/* Dark mode */
--primary-text: #f5f5f5; --primary: #7ba3f7; --accent: #e91e8c;
--extra-one: #1e2a4a; --extra-two: #3d1e2e; --extra-three: #1e3020;
--error: #f44336; --elevation-level-1: #121212; --footer-bg: #0d0d0d;
--section-hero-bg: #0f172a;
/* Proposed, pending approval */
--fold-grey: #5b5957; /* secondary text, 7.03:1 on white */
/* Builder marker-type default (fallback, not brand) */
default_color #3B82F6 selection_color #2563EB
reverse_color #1E40AF reverse_selection_color #1E3A8A
icon_color #FFFFFF reverse_icon_color #000000
advanced_marker_type circlePoint border_style true
Contrast reference
Measured WCAG 2.2 contrast ratios for the pairings people actually reach for. Body text needs 4.5:1. Large text and meaningful graphics, including marker icons, need 3:1.
| Pairing | Ratio | Allowed for |
|---|---|---|
| AaText on white | 16.29:1 | All text |
| AaFacet Magenta on white | 5.96:1 | All text |
| AaFold Grey on white (pending) | 6.97:1 | All text |
| AaText on Map Blue | 4.89:1 | All text |
| AaWhite on Facet Magenta | 5.96:1 | All text |
| AaWhite on Night | 17.85:1 | All text |
| AaDark Mode Blue on Night | 7.16:1 | All text |
| AaWhite on Footer | 16.67:1 | All text |
| AaFacet Magenta on Blue tint | 5.11:1 | All text |
| AaText on Pink tint | 12.46:1 | All text |
| AaError on white | 7.33:1 | All text |
| AaWhite on Map Blue | 3.33:1 | Large text (18.5 px bold or 24 px+), marker icons and graphics |
| AaMap Blue on white | 3.33:1 | Large text (18.5 px bold or 24 px+), marker icons and graphics |
| AaMed Grey on white | 3.40:1 | Large text (18.5 px bold or 24 px+), marker icons and graphics |
| AaWhite on Success | 2.69:1 | Fails. Decorative fills only |
| AaDark Mode Magenta on Footer | 3.99:1 | Large text (18.5 px bold or 24 px+), marker icons and graphics |
Logos are exempt from contrast requirements, but the colourway rules in Section 04 still apply.
Changelog
What changed and when. The version on the cover always matches the top line here.
| Version | Date | Change |
|---|---|---|
| 1.0 | October 2026 | First release. Collects the existing logo files, site colour and type tokens, the current basemap catalogue, marker type rules from the builder, and the illustrated map pipeline into one guide, aligned with the Mobiddiction master guide v1.6. Adds proposed clear space, minimum sizes, a secondary text grey and the map grid device, all pending approval. |