Auto (balance) mode: replace current strategies with clearer goal-based modes

Open
#2,522 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
dart, flutter
Domain
design, frontend

Research direction

Read the related issue #2502 for the balancer tuning plumbing and first-alive strategy mentioned here. Then trace how Auto (balance) strategies are presented and mapped to balancer or url-test parameters in the app; the issue does not name files or tests. Done means replacing the confusing strategy choices with the proposed goal-based modes and their intended connection priorities.

Written by the indexing model from the issue text.

Description

enhancement need_attention

Summary

Feedback on the Auto (balance) mode from support experience with thousands of users: the current strategies are confusing and in practice don't work well. Almost every user with connection problems was fixed by switching to lowest (lowest ping) or selecting a config manually.

Problems with the current options

  • Round-robin rotation between configs, the strategy that picks a config based on logs/history, and sticking to one config look good on paper but do not give a good user experience.
  • The names and differences are unclear to normal users.
  • The rest of the app is clear and simple; this part is the exception.

Suggested alternative modes (user-facing, outcome-based)

  • Best Stability: most stable connection
  • Highest Speed: highest throughput
  • First Alive: first healthy server
  • Gaming Mode: prioritise latency and jitter
  • Streaming Mode: prioritise speed and stability

Each mode can map to existing balancer/url-test parameters internally; the user only sees the goal.

Related

  • #2502 (balancer tuning plumbing, first-alive strategy)
Dominant language
Dart
Stars
33.9k
Forks
3.2k
Avg merge
9h 34m
Merged PRs (30d)
22

Getting set up

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 hiddify/hiddify-app

All issues in hiddify/hiddify-app

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.