New user - first feedback

Astrion
1

Feedback: Really impressed so far – a few suggestions

First off, really impressed with Astrion and RosCard. I’m still very much learning (only day 2!), but I’ve already managed to set up:

  • Activity-based control (similar to Harmony) using scripts
  • Device control, lighting, and Apple TV navigation
  • An IR-controlled device (projector) via MQTT, including state tracking

So overall, a great experience so far.

A few usability improvements that would make a big difference:

1. Larger font options

Even with font size set to maximum, the text is still quite small on the screen.

  • Would be great to have a larger scale option
  • Particularly helpful for readability at a distance

2. Small / awkward tap targets (two-dot menu)

Some cards require tapping the two dots in the top right.

  • The tap area is very small
  • Difficult to hit reliably
  • Especially awkward as a left-handed user

A larger touch target or alternative interaction would help a lot here.

3. Global button mappings

I’d like to be able to define default behaviours for buttons, regardless of which card is active.

Example:

  • Volume buttons always control amplifier volume

Some buttons allow this already, but not consistently across all controls.

4. Navigate to another card after an action

It would be really useful to jump to a specific card after running a script or activity.

Example:

  • Press “Watch TV”
  • Automatically switch to Apple TV control card

This would make activity flows much smoother.

5. Swipe navigation between screens

Currently switching screens via the top selector is quite fiddly.

  • The touch target is small
  • Would be much nicer to swipe left/right between screens

6. More flexible button sizing/layout

Some buttons (e.g. activity buttons) are quite large vertically.

  • Only a few fit on screen at once
  • Would be great to control size / density
  • More compact layouts would improve usability

7. More advanced hardware button actions

It would be great to support:

  • Long press
  • Double press

for hardware buttons, not just single press.

This would massively increase flexibility without adding UI clutter.

8. Protective case / 3D print option

The controller feels very well built and premium, but I’d be concerned about damage if dropped.

  • Are there plans to offer a silicone-style protective case?
  • Alternatively, would you consider providing a 3D-printable case file for users?

Overall

Really enjoying the system — it’s powerful and flexible, and already a great Home Assistant companion.

These tweaks would make it even more usable day-to-day.

2 Likes
2

Hi Adam — welcome to the community, and thank you for such thoughtful early feedback :raising_hands:

Honestly, this is exactly the kind of post we love to see from new users: real setup experience, practical observations, and constructive suggestions.

It’s great to hear that within only two days you already have:

:white_check_mark: Activity-style control
:white_check_mark: Apple TV navigation
:white_check_mark: Lighting & device integration
:white_check_mark: MQTT + IR device with state tracking

That’s very much the spirit of Astrion — letting Home Assistant remain the automation brain while the remote becomes a flexible physical interface.

Let me respond to your points one by one.

:one: Larger Font Options

You’re absolutely right.

Current font scaling was designed conservatively to maintain layout consistency, but we are already evaluating:

  • Larger accessibility scaling

  • Distance-view readability modes

  • Improved typography balance

This is a common request and already on our UI refinement list.

:two: Two-Dot Menu Tap Target

Good catch — and especially valuable feedback regarding left-handed use.

We agree the hit area is currently too small.
Upcoming UI adjustments will likely include:

  • Larger touch targets

  • Alternative gesture access

  • Reduced reliance on precision tapping

:three: Global Button Mapping

This is one of the most requested advanced features.

What you’re describing is essentially:

:backhand_index_pointing_right: Context-independent hardware behaviour

Example:

  • Volume → always amplifier

  • Power → global OFF

  • Navigation context retained across cards

We are actively evolving toward a global hardware mapping layer so users can define persistent button behaviour independent of the active card.

:four: Navigate to Another Card After Action

Yes — this aligns perfectly with the “Activity → Control Context” workflow many users want.

Your example:

Watch TV → automatically open Apple TV card

is exactly how traditional activity remotes behave.

We are exploring mechanisms for:

  • Script-triggered card switching

  • Activity state awareness

  • Context auto-loading

This is a key usability milestone for Astrion.

:five: Swipe Navigation Between Screens

Excellent suggestion.

You’re not alone — many users instinctively try to swipe.

We are evaluating gesture navigation carefully because gestures must not conflict with scrolling or accidental triggers, but swipe-based page navigation is definitely under consideration.

:six: Flexible Button Layout / Density

Agreed.

Current layouts prioritize clarity and touch accuracy, but power users quickly want higher information density.

Future directions include:

  • Compact layout modes

  • Adjustable button sizing

  • More customizable grid behaviour

:seven: Advanced Hardware Button Actions

Long press and double press support is something we also want internally.

Adding multi-action hardware behaviour dramatically expands capability without increasing UI complexity — especially for advanced Home Assistant users.

This is part of longer-term input system expansion.

:eight: Protective Case / 3D Print Option

Great question.

We understand the concern — the remote is designed as a premium daily-use device.

We are currently evaluating:

  • Protective accessories

  • Community-friendly options such as 3D-printable cases

No announcement yet, but it’s definitely being discussed.

:star: Overall

Your feedback touches almost perfectly on the areas we are currently refining:

Phase now = usability + workflow maturity, not just adding features.

Astrion is still very young compared to legacy remotes, so posts like yours directly influence development priorities.

Thank you again for taking the time to share detailed impressions — and please keep the feedback coming as you continue exploring.

— Charles
Sanytron / Astrion Team