Hubbaly
Go to app
All updates

UX improvements, Joining emails, Photos, simpler Account and Event pages

Hubs can tailor key joining emails, pasted links recognise the right service, personal settings come together on Account, event pages fit phones better, and album photos fill in without a refresh.

  • communications
  • hubs
  • invites
  • events
  • photos
  • payments
  • tickets
  • admin
  • reliability

Joining and invitations

  • Email Studio -> Joining emails now holds two reusable hub emails: Application accepted and Import invitation. Owners and admins can keep Hubbaly’s version or save their own subject, heading and formatted message, choose the current hub banner, compare the exact desktop and phone versions, and send a test to themselves.
  • Hubbaly keeps the important joining facts, expiry, action and email controls fixed. Links and simple formatting are supported, while images inside the organiser’s message are left out so the email stays dependable.
  • The application email gives an existing account holder Open hub and gives someone without an account Accept invite. Import review freezes the chosen version so the first invitation, reminders and resends continue to match even if the hub template changes later.
  • The request-submitted screen can show an optional hub message beneath the fixed confirmation and next step.
  • Direct hub invitations now open on a page with the hub’s banner, logo, colours, full description, current rules and terms. An invitation that bypasses approval can join directly. Otherwise, the recipient completes the hub’s current request or application form and sends it for approval.
  • On the hub page and in your invitations, an invitation that still needs approval now reads Review and apply rather than Accept, and opens the invitation so you can complete the hub’s form first. An invitation that does not need approval still joins in one tap.
  • Applying from an invitation now finishes on the same Request Submitted screen and organiser message as applying from the hub itself, and the used invitation and its end date are no longer shown once the request is in.
  • A signed-out recipient keeps the full branded overview before signing in, a part-finished application survives a reload, and the public preview of an invitation never shows the invited email address.
  • Member import now asks whether to send invitation emails on the final Confirm step, beside the reviewed counts, as two plain choices instead of a dropdown. Changing the choice refreshes the review before the import can start.
  • An imported-member invitation no longer asks the person to check their details when the import carries only the hub’s own private records, because there is nothing for them to confirm.
  • An imported member now agrees to Hub Rules and the Membership terms and privacy notice separately, the same as anyone applying normally, instead of one combined notice. Each acceptance is checked against the version of the document in force at the time.
  • Application review now shows that the applicant agreed to the hub’s membership terms and privacy notice, beside their answers.
  • The Joining emails editor now runs in the order the message reads: inbox subject, email heading, hub banner, then your own message. The banner setting offers explicit Use hub banner and Do not use hub banner choices, and the preview heading and size controls stay in view while you scroll.
  • Direct invitation emails are shorter and clearer about who invited the person, which hub they are joining, when the invitation ends and what to do next.
  • Dates and times throughout Hubbaly emails now read in plain English UK time, such as 29 Sept 2026 at 1:12 pm, rather than as machine timestamps.

Alerts about join requests

  • Account -> Notifications now separates New join requests from Your join requests. An organiser can switch off alerts about people applying to their hub without also losing updates about their own requests, and each has its own In-app, Push and Email choice. Existing choices carry across to the organiser one.
  • Join requests, approvals and decisions now appear as in-app alerts the moment they arrive, when you have in-app alerts switched on for them.
  • Two people applying to the same hub now raise two separate alerts on your phone.

Hub links

  • Adding a hub link is now paste-first. Enter a website, profile or email address and Hubbaly recognises services including Facebook, TikTok, WhatsApp, Meetup, Eventbrite, Linktree, Patreon, Substack, Spotify, SoundCloud, Bandcamp, Twitch, Vimeo and Strava.
  • A recognised link gets the right mark and a useful default label. Saved links are shown as one clean, aligned list, and opaque profile identifiers are hidden when they would not help a visitor.
  • Featured links still keep their emphasis, while every row follows the same visual rhythm. The separate kind picker and bordered links box have gone.

Account

  • The Account tab is now the one home for everything about you. Your name and photo sit at the top with three equal actions: Edit profile, View and Share.
  • Notifications, safety, password, sign-in and chat settings are one tap below. The old Settings page now takes you to Account, each settings page has one clear name and back link, and the Account tab stays selected throughout.
  • Your own profile uses a labelled Edit profile link instead of a small pencil icon.
  • Share now opens a panel led by your connect code, with anyone waiting to connect shown directly beneath it, so a request that arrives while you are holding your phone out is visible without scrolling. Sending your link is now just Share and Copy link, because your phone’s own sharing menu already covers the rest.

Event and hub pages

  • Event pages now say Hosted by {hub} above the title, with the hub name as a clear link when its page is available. Signed-out visitors also get an Events link back to that hub’s event list.
  • When an open hub sells members-only tickets, the ticket card gives people who only need membership a direct Join {hub} without buying a ticket route.
  • On phones, event dates use a shorter form, the date and place use the full width, and Calendar and Share event sit together above the main ticket action. The header is about a third shorter while tablet and desktop layouts stay the same.
  • The Attendees card now follows the same layout as the rest of the event page, keeps actions readable on narrow screens and leaves member-facing attendance privacy unchanged. Organiser actions align consistently on the right.
  • Hub event cards on Overview and Events give the event name, date and place the full text width on phones. Status labels sit in a footer with the organiser action on the right; Open Event Day keeps the bold action, while Manage Event and Show report use the quieter style. On member overviews, the whole row opens the event, so the redundant View button has gone.
  • Hub overviews no longer place Report this hub beneath the hub’s own links. Reporting remains available in the places where someone is reporting specific content or behaviour.

Photos, payments and ticket reliability

  • Upload a batch to an album and each picture appears as soon as its thumbnail and preview are ready. Closing the upload panel, scrolling away, reloading the page or opening a picture does not stop the remaining tiles from filling in.
  • A slow or late response cannot blank a picture that has already arrived, and the upload finishes only once the usable previews are ready.
  • Connecting, managing and disconnecting a hub’s Stripe account now belongs to the hub owner. Admins and managers can still see whether payments are ready, while the connected account’s email address is visible to the owner alone.
  • A new owner can start payment setup straight away, including after a previous owner disconnected. Ownership is checked again before a Stripe change is saved, so a handover during a slow request cannot give the old owner control.
  • Held returned tickets stay available to the person they were offered to, respect their deadline, and no longer let sold-out or removed choices use capacity.
  • A temporarily unavailable hub banner is retried after navigation instead of immediately being replaced with generated artwork.

Behind the scenes

Joining-email choices are stored as immutable hub revisions so a reviewed import cannot change underneath the people receiving it. Invitation application answers keep their encrypted form version and snapshots with the pending request. Album processing uses stable, bounded checks across page and picture changes. Stripe ownership and held-ticket capacity are rechecked at the point of change. Production and staging API hosts also have bounded request logs for incident work without storing query strings or request headers. Split join-request alert topics snapshot every effective channel before either side is first edited, so switching one off cannot quietly re-couple them.

Keep up with what we ship

Follow new releases by email or feed.

RSSAtom