3
20
Fork
You've already forked paiesque
1

Feedback after initial usage #32

Open
opened 2026年04月27日 19:43:02 +02:00 by m4callik · 1 comment

Great app idea. Sharing some feedback while it's fresh:

  1. Could you move the Legend above the chart instead of below: New users don't know how to interpret the data, so the legend helps out a lot, but currently the user has to scroll to see it (attached examples). I like that it's collapsed by default tho
  2. Additionally/alternatively, I had to read the README to figure out the Settings. It turns out that this is also in the Help section but perhaps it could be promoted as a root option for new users that have no idea what they're reading (markdown rework below)
  3. Maybe an adjustment so the chart axes only calls out every Sunday or milestones or every other day: Might reduce some of the current clutter
  4. On a related note, having the chart axes use both DoW and dd/mm/yy also adds to the clutter a bit. One option is to have DoW, and then every Sunday has the dd/mm/yy perhaps

Hamburger Settings reorg example

- Introduction/Reading the Data
 - <insert current 'Help' section>
- Help
 - View Logs
 - Bug Report
Great app idea. Sharing some feedback while it's fresh: 1. Could you move the Legend _above_ the chart instead of below: New users don't know how to interpret the data, so the legend helps out a lot, but currently the user has to scroll to see it (attached examples). I like that it's collapsed by default tho 2. Additionally/alternatively, I had to read the README to figure out the Settings. It turns out that this is also in the `Help` section but perhaps it could be promoted as a root option for new users that have no idea what they're reading (markdown rework below) 2. Maybe an adjustment so the chart axes only calls out every Sunday or milestones or every other day: Might reduce some of the current clutter 3. On a related note, having the chart axes use both DoW and dd/mm/yy also adds to the clutter a bit. One option is to have DoW, and then every Sunday has the dd/mm/yy perhaps **Hamburger Settings reorg example** ```markdown - Introduction/Reading the Data - <insert current 'Help' section> - Help - View Logs - Bug Report ```

Thanks for the thoughtful feedback! Let me address each point and share some context.

Legend position

The legend was intentionally placed below the chart so that the chart remains the first thing you see when opening the app – the data comes first, the explanation follows. Moving it above would push the chart down, especially since the legend can become quite long when many layers are active. That said, I understand the desire to see it immediately. A possible compromise could be to show a single‐line hint below the layer buttons that briefly explains what's currently displayed. Let's see if others feel the same way.

Help / Settings discoverability

The help section (accessible from the overflow menu) contains both usage guidance and scientific references. I agree it could be made more prominent, maybe through an onboarding flow for new users, or a dedicated "Learn" entry in the main menu. If there's a consensus on the best approach, we could improve this.

Chart axis labels

The current implementation uses androidsvg, which has limited text layout capabilities – labels can overlap if there are too many dates. The app already skips labels to maintain a minimum spacing, but with long date ranges (e.g., a full year) the result can indeed look cluttered. Switching to a format like "day of week + date only on Sundays" is an interesting idea but would need to be tested across different date ranges and languages. Before doing changes the rules needs to be explored further. (The SVG chart generation is already quite complex.)

Next steps

I suggest we keep this issue open for now to collect more ideas and see which changes resonate with the community. If a particular improvement gets multiple requests, we can prioritise it. Thanks again for the detailed suggestions!

Thanks for the thoughtful feedback! Let me address each point and share some context. ### Legend position The legend was intentionally placed below the chart so that the chart remains the first thing you see when opening the app – the data comes first, the explanation follows. Moving it above would push the chart down, especially since the legend can become quite long when many layers are active. That said, I understand the desire to see it immediately. A possible compromise could be to show a single‐line hint below the layer buttons that briefly explains what's currently displayed. Let's see if others feel the same way. ### Help / Settings discoverability The help section (accessible from the overflow menu) contains both usage guidance and scientific references. I agree it could be made more prominent, maybe through an onboarding flow for new users, or a dedicated "Learn" entry in the main menu. If there's a consensus on the best approach, we could improve this. ### Chart axis labels The current implementation uses `androidsvg`, which has limited text layout capabilities – labels can overlap if there are too many dates. The app already skips labels to maintain a minimum spacing, but with long date ranges (e.g., a full year) the result can indeed look cluttered. Switching to a format like "day of week + date only on Sundays" is an interesting idea but would need to be tested across different date ranges and languages. Before doing changes the rules needs to be explored further. (The SVG chart generation is already quite complex.) ### Next steps I suggest we keep this issue open for now to collect more ideas and see which changes resonate with the community. If a particular improvement gets multiple requests, we can prioritise it. Thanks again for the detailed suggestions!
Sign in to join this conversation.
No Branch/Tag specified
main
main_chart
feature/offline-maps
v89
v88
v87
v86
v85
v84
v83
v82
v81
v80
v79
v78
v77
v76
v75
v74
v73
v72
v71
v70
v69
v68
v67
v66
v65
v64
v63
v62
v61
v60
v59
v58
v57
v56
v55
v54
v53
v52
v51
v50
v49
v48
v47
v46
v45
v44
v43
v42
v41
v40
v39
v38
v37
v36
v35
v34
v33
v32
v31
v30
v29
v28
v27
v26
v25
v24
v23
v22
v21
v20
v19
v18
v17
v16
v15
v14
v13
v12
v1.10
v1.9
v1.8
v1.7
v1.6
v1.5
v1.4
v1.3
v1.2
v1.1
v1.0
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ojrandom/paiesque#32
Reference in a new issue
ojrandom/paiesque
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?