Hello,
Just noticed this the other day as I switched from Heliboard to Gboard. I have the same vibration settings on both (30 ms), but Gboard just feels more responsive, while Heliboard feels kind of clunky.
Does anybody experience the same? Can anything be done about it?
You must log in or # to comment.
Well, a bit maybe, yes
But most annoying is the swipe detection, which feels much more stubborn
English is quite ok, but else… Especially mixed languages don’t work well, and I’m always having to switch between German and EnglishHeliboard also has weird bugs such as scrubbing through text with the space not working sometimes, even duplicating letters at times. But overall it works great.
To answer your question with another question: Heliboard isn’t the same code base as GBoard, isn’t it? Which means that it might have some kinks to iron out to feel more responsive.
To answer your question with another question: Heliboard isn’t the same code base as GBoard, isn’t it?
Well, indeed. I was just hoping that someone expert on the intricate inner mechanisms of GBoard could have explained why the comparison is so striking
A bit of necromancy is always appreciated. I second handed some learning about Android APIs and especially rumble. It’s really scattered and for a very specific vibration you have to basically go very low and code it yourself.
Which might be why Heliboard isn’t as polished as Google Board. They might be using simpler API and Google might be using its engineering for a perfect feeling.
I tried on my pixel and it seems as snappy as gboard, thinking to switch. Although i didn’t load extra dictionaries or the proprietary swipe module
I’ve just been using gboard with no internet
For one gboard has been longer in existence compared to heliboard. Heliboard still has quirks to fix which will take some time.
