Android
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
🔗Universal Link: !android@lemdro.id
💡Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
📰Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
-
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
view the rest of the comments
Thanks!
More octaves is the very next thing to add. Not sure about the UI though. Screen real estate is scarce. One idea is to just remove the "Piano" word and add there two buttons for octaves, or add a settings cogwheel in place of the volume that opens a pop-up with both volume and octaves. This second option is probably better in the long term if more settings are added like different instruments.
I'm open to suggestions though!
I think you're right that some kind of "menu" button that presents additional options would be best. Eventually there will be other options and it will be necessary..
I think most people will adjust the volume once, but may want to change the octave while playing. If my assumptions are right, the octave change feature should be the most accessible one, replacing the current volume buttons. The volume, and any other features could be handled through the menu button.
My ideal solution would be to provide a menu button and two function buttons. Then have a menu option to configure whether the functions buttons acted as octave up/down, volume up/down, or controls for whatever additional features get added.
I'd also like to put in a pitch to add support for the "scrolling" feature that some watches now have. It could control the opposite feature of whatever is assigned to the function buttons, making it possible to adjust both octave and volume on the fly. It does seem like it should be a lower level priority, since not all watches support that feature.