Report from this weekend’s community call:
- We started off with introductions as @viariable joined us for the first time. We also discussed a bit the point & content of these meetings, vs the ‘Needs: Decision’ meetings.
- Then moved on to discuss the state of the player screen UX/design. That work is ongoing by me and two UX designers - we’re posting updates in Player screen UX/UI work. We’re actively working but I suspect it’ll be some month before this is actually implemented. @viariable was asking because of their proposal in Instead of the generic button name "Chapters" show currently playing chapter name · Issue #6249 · AntennaPod/AntennaPod · GitHub; whether it could be accepted as an intermediary improvement. I explained I didn’t see this possible for 2 reasons:
- we’re in the middle of a release roll-out and the next one will be a while (and then we might be already close to the player screen improvements)
- we wouldn’t want to make some changes to the player screen now (which users have to get used to) only to change it again soon.
- In context of the previous point, we briefly discussed the 3.7 release:
- We found @loucasal so kind to prepare release notes
- This version is currently being rolled out to 5% of Google Play users
- We found @loucasal so kind to prepare release notes
- @viariable also asked about Redesign the player icons to eliminate sharp edges / be rounder · Issue #7062 · AntennaPod/AntennaPod · GitHub. The proposal there uses https://phosphoricons.com. We went through some of the pain points of the proposal: can’t use an ‘ear’ as we also have video podcasts, we have to increase the line thickness to ensure visibility, there are some other icons that I created manually as there were no existing icons so we might have to do the same (or request upstream, although there’s a lot of requests already). Probably best to discuss at the next Needs Decision meeting.
- They also brought up Highlight plain-text links in episode description by viariable · Pull Request #7581 · AntennaPod/AntennaPod · GitHub, but as I have no clue about development, best to discuss that also when @ByteHamster is in the meeting (e.g. Needs Decision).
- @cos brought up Please notify user after having moved a corrupt database [has-patch]. We discussed whether and concluded that there’s still a point in more elegantly handling database corruptions, because it still happens occasionally. The patch would need further changes as it leverages the empty state screen (the one after fresh install) but we don’t have that one any-more. We should also update the website text (‘run this python script or ask us in the forum to do it for you’) as currently it’s a bit wooly and doesn’t link to the correction script. The UX idea now:
- Title block: Oh no, AntennaPod crashed!
- Explanation: [concisely: what happened & why, and how to recover]
- Buttons:
- Export/Share database
- Read more