Pin Placement — Cross-Platform UX Audit

At a glance

Flow steps audited

11

2 required · 9 optional · 2 hidden

Critical gaps

14

Missing or broken on at least one platform

Friction points

27

Unnecessary clicks, unclear patterns, modal overhead

Alignment opportunities

6

Cross-platform patterns worth standardizing

Platform snapshot

How each platform fares

Each bar segment represents one step of the flow. The health of each platform is strongest where core placement works (Web) and weakest where organisational actions — groups, subscriptions, bulk management — are missing altogether (Android).

🖥 WEB / DESKTOP

Web

9/ 11 steps covered

Only platform with a clear "New Pin" CTA
No pin templates, no quick actions
Heaviest reliance on modal confirmations

📋 IOS TABLET

iPad

10/ 11 steps covered

Strongest placement ergonomics (long-tap + quick dial)
Offers templates & quick actions unique to it
No project settings access, no Group action

📋 ANDROID TABLET

Android Tablet

7/ 11 steps covered

Pin always spawns at screen center, ignoring tap location
No quick actions, no templates, no title suggestions
Most divergent from iOS siblings

📱 IOS PHONE

iPhone

8/ 11 steps covered

Preserves core mobile patterns from iPad
Loses quick-action dial despite being mobile-first
Pin panel fills screen, blocks continued work

📱 ANDROID PHONE

Android Phone

6/ 11 steps covered

Narrowest surface area overall
No Pin context menu, no Groups, no Subscribe
Taps still ignored for placement

The matrix

Flow, step by step, platform by platform

Each row is one step in the Pin placement flow; each column is one platform. Severity dots flag the state of that step on that platform: ● healthy, ● friction, ● critical gap, ● not available.

● Works as expected ● Friction / inconsistency ● Critical gap or bug — Not available REQ Required OPT Optional HIDDEN

Step	WebDESKTOP	iPadIOS TAB	Android TabTABLET	iPhoneIOS PHONE	AndroidPHONE
01 Enter placement flow Required Initiate the creation of a new Pin on a plan.	● Clear "New Pin" CTA top-left. Confirm/cancel below preview.	● Long-tap places pin at tap location. Rich quick-action dial (templates T1/T2/T3, pin+task, pin+photo) — but no UI trigger and T1/T2/T3 labels are opaque.	● Long-tap only, and pin spawns at screen center, not at tap. No quick actions. No templates.	● Long-tap honors tap location, but quick-action dial is missing compared to iPad sibling.	● Same as Android tablet — long-tap, center placement, no quick actions.
02 Confirm Pin position Required Attach the Pin to the correct point of interest.	● Drag-to-position with dedicated zoom controls. Cannot tap-to-place — drag is only option.	● Tap-to-place supported. Pinch-zoom, no visible zoom controls.	● No tap-to-place. Drag-only. No zoom controls.	● Tap-to-place works. No visible zoom controls.	● No tap-to-place. Drag-only. No zoom controls.
03 Set Pin title Required Give the Pin a meaningful label.	● Input + recent titles. Only a close button — no explicit save/confirm.	● Input + recent titles + explicit Cancel/Save. Clearest pattern.	● Input only — no recent titles. Panel height/behavior diverges from iOS.	● Input + recent titles + Cancel/Done actions.	● Input + recent titles + Cancel/Done actions.
04 Set Pin category Optional Define the right type of work or issue.	● Looks like a dropdown, behaves like a modal. 3 clicks — requires explicit "Okay" confirm.	● 2 clicks (better pattern) but no project-settings access — can't change the default.	● 2 clicks, no project-settings access.	● 2 clicks, no project-settings access.	● 2 clicks, no project-settings access.
05 Create task within Pin Optional Assign specific actions and due dates.	● 6 clicks min. Extra "Save" after date selection adds friction.	● 8 clicks. 🐛 Label typo ("Create new tasks"). Keyboard blocks controls. Extra state-legend affordance.	● Same as iPad — 8 clicks, label typo, keyboard overlap.	● 6 clicks. Label typo persists. Extra state legend.	● 6 clicks. Label typo. State legend.
06 Attach data from dataset Optional Pull measurements or details from imported documents.	● Dedicated "Add dataset link…" action — only appears when a dataset exists (poor discoverability).	● Datasets exposed inline in fields; supports multi-select. No explicit save (Back closes).	● Inline + multi-select + sorting. Most capable implementation.	● Inline + multi-select + sorting.	● Inline + multi-select + sorting.
07 Set Pin fields Optional Fill custom fields defined in project settings.	● Inconsistent layouts across field types (label-above vs label-beside).	● Same inconsistency as Web.	● Same inconsistency as Web.	● Same inconsistency as Web.	● Same inconsistency as Web.
08 Add a note Optional Share updates, photos, audio, materials.	● "Attach" morphs into "Submit" once typing starts — breaks mental model.	● Same Attach/Submit morph. Quick-photo action added.	● Only text or photo — other attachments unsupported.	● Only text or photo supported.	● Only text or photo supported.
09 Add Pin to a group Optional Hidden Organise Pins for reporting and management.	● Buried in overflow menu. 4 clicks. No visual indicator of group membership.	● Not available in plan view — only via Pin list.	● Not available at all. No Pin list view, no context menu.	● 4 clicks via context menu. No group-membership indicator.	● Not available. No context menu at all.
10 Subscribe to a Pin Optional Hidden Receive updates on Pin activity.	● Hidden in overflow menu. No "not subscribed" state visible until action is taken.	● Not available.	● Not available.	● Not available.	● Not available.
11 Continue work Optional Proceed to next pin or activity.	● Button-only close.	● Button or tap outside — best pattern, worth porting.	● Button-only close.	● Panel fills screen; close button or swipe-down required.	● Panel fully blocks screen; button-only close.

Patterns & themes

Six recurring stories

Stepping back from per-row detail, the gaps cluster into six patterns. Each theme is independently actionable and maps to multiple steps in the matrix.

THEME · 01

Mobile has no "New Pin" entry point

High impact

Every mobile platform relies on long-tap as the sole trigger for Pin creation. Experienced users adapt; new or less tech-savvy users have no visible affordance at all. Consider a persistent FAB or category-specific entry buttons that pre-seed title, template, and defaults.

Affects: Step 01 · iPad · Android Tab · iPhone · Android Phone

THEME · 02

Placement precision is inconsistent

High impact

On iOS devices, tapping a spot on the plan drops the Pin there. On Android, the Pin always materialises at screen centre — requiring the user to drag every time. A consistent "tap where you mean" model across all platforms would cut effort for a high-frequency action.

Affects: Steps 01–02 · Android Tab · Android Phone

THEME · 03

Unnecessary confirm steps add drag

Medium impact

Category selection, date picking, and title entry all introduce an explicit "Okay" / "Save" step on Web, inflating click counts. Selection-is-confirmation (as on iPad for category) is cleaner and worth making the standard — with undo where stakes are higher.

Affects: Steps 03–05 · all platforms, most pronounced on Web

THEME · 04

Organisation actions are hidden or missing

High impact

Groups and Subscribe — core Pin-organisation primitives — are buried in a 4-click overflow menu on Web/iPhone, absent on iPad, Android Tablet, and Android Phone. They also lack visible state ("am I subscribed?" / "which group is this in?"). Promote both into the Pin panel as always-visible controls with state indicators.

Affects: Steps 09–10 · all platforms

THEME · 05

Android is drifting from iOS

High impact

Android tablet and phone lack quick-action dials, Pin context menus, Groups, Subscribe, recent-title suggestions, and tap-to-place. The platform gap is wide enough that an Android customer has materially less product than an iPad customer. Close this gap as a dedicated workstream.

Affects: Steps 01, 03, 09–11 · Android Tab · Android Phone

THEME · 06

Notes lose capability on mobile

Medium impact

Web and iPad support rich attachments alongside notes; iPhone and Android are restricted to text or a single photo. On all platforms, the "Attach" button transforms into "Submit" when the user starts typing, violating convention and making it impossible to compose text and attach media in a single note.

Affects: Step 08 · all platforms, most restricted on Android & iPhone

Recommendations

What to change, in priority order

Each recommendation maps to one or more themes and spans multiple platforms. Impact is our estimate of user-value; effort is a rough design-and-engineering size, not a commitment.

#	Recommendation	Impact	Platforms	Themes
R1	Introduce a persistent "New Pin" entry on all platforms A FAB or category-segmented CTA that gives new users a visible trigger, while keeping long-tap as the power-user shortcut. Allow each category to carry its own defaults (title, template, subscribe).	High	iPad · Android · iPhone	T1
R2	Make Android pin placement honor tap location Match iOS behavior so the Pin drops where the user tapped, not at screen centre. Resolves a high-frequency friction point for a large portion of the user base.	High	Android Tab · Android Phone	T2, T5
R3	Promote Group & Subscribe to first-class Pin controls Surface both as always-visible affordances in the Pin panel, with clear state indicators (group chip, bell with active/inactive state). Remove them from overflow menus. Replicate across all platforms.	High	All platforms	T4, T5
R4	Eliminate redundant "Okay/Save" confirmations Adopt selection-as-confirmation (as on iPad) for category, date, and dataset-link pickers. Provide clear undo rather than modal friction. Standardise across platforms.	Med	Web primarily	T3
R5	Bring Android to feature parity with iOS Quick-action dial, Pin context menu, recent-title suggestions, Pin list view, bulk actions. Treat as a coordinated Android workstream rather than ad-hoc fixes.	High	Android Tab · Android Phone	T1, T5, T6
R6	Fix the note "Attach → Submit" morph Keep Attach and Submit as distinct actions regardless of typing state, so users can attach media and write text in a single note. Align attachment capabilities between Web, iOS, and Android.	Med	All platforms	T6
R7	Extend pin templates & quick actions to Web & Android The iPad's template + quick-action model (create-with-photo, create-with-task) is the strongest pattern in the audit. Rename T1/T2/T3 to template-chosen names and expose the model on other platforms. Let project admins curate templates and recent titles.	High	Web · Android · iPhone	T1, T5
R8	Adopt "tap-outside-to-close" on Web A small but consistent polish — iPad already behaves this way. Reduces friction for users who want to keep placing pins in rapid succession.	Low	Web	T3
R9	Fix bug: "Create new tasks" label Button is labelled "Create new tasks" (plural) on iOS and Android — should match Web's "task". Tiny fix, better cross-platform hygiene.	Low	All mobile	—

Open questions for research

What we don't yet know

Questions that emerged from the audit and are better answered by user research than design debate.

How do users currently use "recent pin titles"? Is it rescue-after-typo, or a genuine shortcut? Could it be replaced with admin-curated templates at the project level?
How many categories do teams typically use, and how stable are they? This shapes whether category selection deserves a dropdown, a pill list, or a visual icon grid.
How frequently do users attach datasets to pins, and is multi-select (on mobile) actually valuable — or did it emerge from engineering convenience?
Do users create tasks during Pin placement or later, in a review pass? The answer determines whether task creation should be front-and-centre or tucked into a secondary flow.
What does "subscribe" actually do from the user's perspective? If it is purely a notifications control, should it be reframed as "Notify me" with clearer consequences?
How often are Pins added to Groups at creation time vs. later? If it's mostly retroactive, a group-selector at creation may be unnecessary weight.
Who creates tasks via Notes, and why — given there is already a dedicated "Create task" action? Are the two paths addressing different jobs-to-be-done?