Feedback

What should we build next?

Browse boards, vote on ideas, share your own.

Theme picker on Profile page (Light / Dark / System)

The Light / Dark / System segmented control was previously only on the standalone Appearance tab. Users naturally look for it on the Profile page first, so it is now embedded directly in /app/account/profile alongside avatar, display name, and username. Extracted the segmented control into a single shared ThemeSegment component so the Profile form, the Appearance tab, the topbar toggle, and the sidebar/user-menu can never drift. Both surfaces auto-subscribe to OS preference changes when System is selected. Removed a personal-name placeholder from the Username input.

TweakShippedGeneral·3 months ago·0

Sidebar collapse toggle: floating chip, modern look

The collapse / expand control had two problems. (1) The lucide PanelLeftClose icon felt heavier than the rest of the portal chrome. (2) The button moved between the brand row (when expanded) and a separate block above the user card (when collapsed), which made it feel like the control jumped down the rail when you clicked it. Replaced both with a single floating chip pinned to the right edge of the sidebar near the top, in the SAME position whether the rail is full-width or a 56px column. Uses ChevronsLeft / ChevronsRight icons for a cleaner Linear / Vercel feel, sits as a small rounded pill with subtle ring + shadow, and hangs half over the border so it reads as a separate floating control rather than another nav row. Also removed overflow-y-auto from the admin rail aside so the chip never scrolls out of view on short viewports.

TweakShippedGeneral·3 months ago·0

Settings sub-nav: API and all config under one Settings surface

The admin sidebar used to expose **API** as its own top-level entry alongside Feedback, Roadmap, etc. Configuration was split across two surfaces (top-level "API" + a separate "Settings" page that only had General). Now the project sidebar focuses on day-to-day work and **every configuration destination lives under Settings** with a shared left-rail nav: General, Privacy & Access, Login & SSO, Domain, Widget, Changelog, Integrations, **API**, Members, Billing, Data, Help. The Settings sidebar item stays active for any nested route. - New shared `settings/layout.tsx` wraps every settings sub-page with the rail - `SettingsNav` highlights the active page (with prefix-match for `/api-keys/*` etc.) - Removed the standalone "API" item from the admin sidebar You only have to learn the word "Settings" once.

TweakShippedGeneral·3 months ago·0

Inline search input in sidebars (with / and ⌘K shortcut hint)

The search trigger was previously a tiny icon-only button tucked into the sidebar header. Discoverability was poor. Both portal sidebars (admin + workspace) now show a **small inline search bar** that: - Reveals the `/` keyboard hint inline - Opens the same command palette modal on click, ⌘/Ctrl + K, or `/` (when no input is focused) - Collapses back to the icon variant when the sidebar is collapsed (see related card) The bar is `variant="bar"` and shares the same `<SearchTrigger>` component used elsewhere, so behaviour stays consistent.

TweakShippedGeneral·3 months ago·0

Support inbox polish: helpdesk layout and message previews

Shipped a production-grade support inbox polish pass inspired by leading help desks. Delivered: - Three-pane inbox layout with ticket list, conversation thread, and details sidebar - Avatars and clearer message bubbles for easier conversation scanning - Ticket properties panel for status, priority, queue, and assignee - Friendlier empty states, composer copy, and threading affordances - Latest-message previews in the ticket list so agents can triage without opening every ticket Release: - GitHub: pushed to master at commit 8cb248a - Production: deployed to https://hollahoop.app

TweakShippedFeature requests·3 months ago·0

Privacy policy: Google OAuth data disclosure for verification

Google's OAuth verification team flagged that the privacy policy at /legal/privacy did not document how the application interacts with Google user data. The policy has been rewritten to satisfy Google API Services User Data Policy requirements. - Explicit table of every Google scope requested (openid / userinfo.email / userinfo.profile) with what each returns and how Hollahoop uses it - Explicit confirmation we do not request Gmail / Drive / Calendar / Contacts / Photos or any sensitive scope - 'What we don''t do' section: no resale, no advertising, no behavioural targeting, no AI/ML training on Google data, no human review (with the standard support / security / legal carve-outs) - Limited Use compliance statement linking to the Google API Services User Data Policy - Sub-processors, cookies, retention (30-day logs, 7-day account delete with up to 30-day backup tail), GDPR rights, contact, last-updated date - Replaced the original 3-paragraph policy with a structured 11-section document

TweakShippedGeneral·3 months ago·0

Support inbox: full-height collapsible filter rail (Linear-style)

**UX audit finding — implemented** The support desk stacked ~220px of header chrome (title, description, 3 filter rows) before the ticket list. Replaced with a full-height collapsible `InboxRail` (264px expanded / 64px icon-only) holding Views, Queues, Status, New ticket, and Settings. List + conversation now use the full canvas height; mobile keeps horizontal filter chips.

TweakShippedFeature requests·3 months ago·0

Roadmap list view: screen readers announce bare vote/comment counts

**UX audit finding** On `/roadmap?view=list`, each row's accessible name concatenates title + vote count + comment count + prioritize count without labels, e.g. "Search upgrade… 0 0 0". Confusing for assistive tech and looks broken in accessibility tree. **Fix:** Add `aria-label` on metric spans (`47 upvotes`, `2 comments`) and hide decorative icons from the name.

TweakShippedBugs·3 months ago·0

Theme toggle aria-label should name the next theme

**UX audit finding** `ThemeToggle` exposes `aria-label="System theme. Click for next."` which doesn't tell screen reader users what will happen. WCAG 2.2: control purpose should be clear. **Fix:** Use `Switch to dark theme` / `Switch to system theme` / `Switch to light theme` based on the next state in the cycle.

TweakShippedBugs·3 months ago·0

Post detail: reduce duplicate Sign in CTAs for anonymous users

**UX audit finding** Post detail shows Sign in in the global header (`UserNav`) AND in the comment composer AND on each thread's "Sign in to reply" link. Three identical CTAs on one page feels noisy. **Fix:** Keep header auth control; change comment composer to a single softer panel ("Join the discussion — sign in to comment") and hide per-comment reply sign-in when the composer already prompts.

TweakShippedFeature requests·3 months ago·0

Feedback post detail: link to roadmap card when item is on roadmap

**UX audit finding** Feedback post detail shows status badge but no deep link to the roadmap card. Users who land from search/votes can't see where the item sits on the public roadmap without manual navigation. **Fix:** When `status.show_on_roadmap`, show a subtle "View on roadmap" link next to the status badge.

TweakShippedFeature requests·3 months ago·0

Docs pages: unify search UX (inline vs header palette)

**Severity:** Medium **Area:** Docs / search Docs now have inline `DocsSearchInput`, but the header still exposes an icon-only `SearchTrigger` that opens the full command palette (posts + changelog + docs). Both respond to ⌘K and `/`, with different scopes. Easy to misunderstand which search you are using. **Fix options:** Hide header search on docs routes, or make ⌘K open inline search only on docs pages.