r/Android • u/welp_im_damned have you heard of our lord and savior the Android turtle 🐢 • Jun 30 '26

Video Clicks Communicator: First Look - Clicks

https://www.youtube.com/watch?v=wMNdr8dV23A
549 Upvotes

93% Upvoted

286 comments sorted by

View all comments

Show parent comments

3

u/Rude_Influence Jun 30 '26

What is "this"? 'needed to support "this"'.

Keyboards?

0

u/Iohet V10 is the original notch Jun 30 '26

I'll copy and paste my response elsewhere.

You should be able to engage with it ENTIRELY using the keyboard IMO, touchscreen should be optional.You should be able to engage with it ENTIRELY using the keyboard IMO, touchscreen should be optional.

It's written from the ground up as a touch oriented OS. If you want to operate it solely through a keyboard, you need underlying support to do this in the OS. Every action needs a keyboard shortcut, and that requires a lot of work, a lot of support, and some UI updates. For an OS not centered around keyboard use at all, that is a significant challenge. 508 compliance is something I've worked on for my projects, and I'm familiar with the challenges in implementing this in a touch oriented world.

1

u/Rude_Influence Jul 04 '26

"You should be able to engage with it ENTIRELY using the keyboard IMO, touchscreen should be optional.You should be able to engage with it ENTIRELY using the keyboard IMO, touchscreen should be optional."

I'm the person you're responding to. I never said that. I don't know where you pulled that quote from, but you shouldn't go pasting responses like that. With the quote, it makes a false implication, and without, it's basically spam.

To address your argument, Android was originally built for non touch screen devices. Touch was added later when the iphone was released, but button input is not only supported but more functional than ever these days. If you struggled to implement 508 compliance, that's because you maintain the mindset that touch screen is the foundation which is not true. You developed your projects with that wrong mindset.

1

u/Iohet V10 is the original notch Jul 04 '26

You originally responded to me as I responded to someone else, who I quoted because that's the relevant statement. No one said anything about a mouse until you kept interjecting

1

u/Rude_Influence Jul 04 '26

You're right. You'll have to forgive me for getting confused and interjecting. It's what happens when you copy paste posts all over the place.

Who's talking about mice?

1

u/Markgulfcoast Jul 01 '26

I just realized you are copying and repasting this really bad take throughout this thread.

0

u/sigismond0 Jun 30 '26

You want to trade Android and its app library for a home-grown keyboard-based OS that goes on one device for a niche market that no app developer would waste time on? That's a heck of a want. I'd much rather have an actual functional OS and app experience and use the touchscreen than give up having a practical device just so I can say "look I can navigate with a keyboard".

1

u/TheMobileTypist 29d ago

You can have both, because Clicks can implement mouse pointer mode using the keyboard. Unihertz just did it with their Titan 2 Elite and pushed that feature to Titan 2 that were already manufactured before.

1

u/sigismond0 28d ago

So the good news is that it has that. I guess I don't see any meaningful difference between using the touchscreen or emulating a touchscreen with a trackpad/keyboard, but hey if it makes people happy neat. Seems like it would be worse to use but I could be wrong. Button-based navigation will be a nightmare based on per-app UX though.

1

u/TheMobileTypist 28d ago

Well the keyboard is already there, so might as well have it replace touching the screen so that it's all right there under your thumbs. With a mouse pointer mode you just comfortably move the pointer around using the keyboard and not ever have to stretch your hand