[FEATURE] Tell people when a better model than theirs is available, and which settings page it lives on

Open
  • Is something wrong?
#1,282 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
swift
Domain
desktop

Research direction

Start with the delete menu in FluidIntelligenceLiveSection.swift, where .disabled(!selected || ...) blocks Delete on unselected models. The badge logic lives in the AI Settings model carousel, and Voice Engine would need a similar hardware check. Done when Delete works on any installed model that isn't selected, and the recommendation notice appears on the Dashboard and the matching settings page. The notice and the page-intro lines are design decisions to confirm with maintainers first.

Written by the indexing model from the issue text.

Description

Problem

FluidVoice has two kinds of models on two pages: speech models in Voice Engine, and cleanup models (Fluid Intelligence) in AI Settings. The release highlight calls Splash a "new cleanup model," but nothing tells you cleanup models live on a different page from speech models.

On 1.6.13-beta.2 I saw the "Meet Fluid 1.1 Splash" release highlight and went looking for Splash in Voice Engine, partly because the same highlight's Fluid Speech Pro card had an "Open Voice Engine" button. It wasn't there, and I was confused. The next day I stumbled on it in AI Settings and switched from Fluid 1 Mini. I'd been running an older cleanup model without knowing a better one was out.

The pieces exist but are easy to miss:

  • The highlight has a "Try Splash" button, and Help > What's new reopens it, but neither tells you that you're on an older model than the one recommended for your Mac.
  • Outside onboarding, the "Recommended for your Mac" badge shows only in the AI Settings model carousel, so you see it only if you already know to go there.
  • Voice Engine has no recommendation badge. I'm still on Parakeet v3. The highlight calls Fluid Speech Pro the most accurate speech model, but Voice Engine doesn't say whether it's the right one for my Mac.

Discussion 758 is another person who couldn't find where to switch models. The reply had to explain that FluidVoice has two separate model settings.

Proposed solution
  1. When the model you're using isn't the one recommended for your Mac, show a small notice on the Dashboard and at the top of the matching settings page: "Splash is recommended for your Mac. You're using Fluid 1 Mini. Switch?" You can dismiss it, and it comes back when a newer model ships.
  2. Add one line at the top of each page saying what its models do: "Speech models turn your voice into text" in Voice Engine, "Cleanup models fix the text afterward" in AI Settings. Each line links to the other page.
  3. Add the "Recommended for your Mac" badge to Voice Engine, using a similar hardware check.
Alternatives considered

Leaving it to release notes and the one-time highlight. That's what I had, and I missed it.

Related: you can't delete the model you just switched away from

After switching to Splash, I wanted to delete Fluid 1 Mini to get its 1.6 GB back. In Mini's "..." menu, "Delete model…" is greyed out with the note "Activate this model to manage it." The menu disables Delete unless the model is the selected one (FluidIntelligenceLiveSection.swift, .disabled(!selected || ...)), so the only way to delete Mini in the app is to switch back to it, delete it, then switch to Splash again (or find its folder through Manage > Open models folder and delete it in Finder).

The models you're not using are the ones you'd want to delete, so Delete should work on every installed model, not just the selected one.

Dominant language
Swift
Stars
11.9k
Forks
863
Avg merge
1d 18h
Merged PRs (30d)
40

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from altic-dev/FluidVoice

All issues in altic-dev/FluidVoice

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.