nullpilot

First of all, congrats for shipping! I am fully on board with the idea that mobile keyboards need some rethinking and hope to see more to happen in that space.

I don't use my phone's default keyboard, but have been locked into a different solution for a while, for better or worse. Allow me to jump straight to the questions.

> Which smartphone keyboard do you use?

I have been using Minuum since I found out there's a version for Android. I had stumbled across the Kickstarter campaign years prior but had forgotten about it until I got a Mini version of a popular smartphone at the time, and the default keyboard took up like half the screen. In a messenger I would see like two lines of the message I am responding to and in terms of user experience it was unacceptable. After making the switch to reclaim some screen estate, and learning about some other neat features (switching between languages with a single swipe was a killer feature at the time, I think Gboard does that now?) it grew on me and I haven't looked back or wished for an alternative once in 7 years or so. It has been unmaintained for years now but I'm still using it. For the peace of mind alone I would happily pay for a maintained version or an alternative, because not having a keyboard I enjoy devalues my phone to the point that I would actively avoid using it, and I am dreading the day I upgrade to a new phone and can't get the same experience anymore.

> Is this something you see as an improvement?

I might just not be the target audience, but I think the approach Minuum took is much more intuitive. It's the exact opposite, the keys are much smaller and put much closer together, but the words I type are almost always recognized, and deleting the word to retry if it's not is fast. The solution provided here is the opposite of what I want personally, provided there is a solution for me that gives me a great experience and free screen estate on top of it.

Also, the thought of using different layouts on mobile vs laptop/PC when my time is split proportionally between the two sounds alienating.

> What features do you enjoy most in a smartphone keyboard? > What other elements of our daily typing experience should be rethought for the digital age?

Screen estate. It's the number one priority besides efficiency imo. The screen should be filled with the things I want to see, not the things I have to see, as much as possible.

Fast dictionary switching. All the communities I interact with are in English. My contacts mostly aren't. This context switch happens frequently, and should be free of needless friction.

Full word deletion to retry if things don't work out. I don't know if it's me or a symptom of the keyboard I use, but deleting words letter by letter is weirdly stressful, especially with auto correct trying to be smart between every keystroke. Being able to have the word gone with one swipe is much closer to the experience I have on the computer keyboard, and I find that to be very reassuring in a way.

> What do you think of the privacy issues surrounding smartphone keyboards?

This is huge. Really. My tolerance for the invasion of privacy keeps dwindling and uncomfortable compromises keep getting more frequent.

Your permission comparison is a big selling point and the main driver that would bring me back to this solution should my preferred option eventually disappear as I dread it will.

Again, thank you for investing time in this space. It's very much needed. Sorry I don't have more positive things to say, but I hope it can still be valuable feedback in some way.

I took the liberty to turn these into a Telegram sticker pack: https://t.me/addstickers/Frontliners (credit included)

Given how TG is being used to spread misinformation, having more positive and helpful content on there can't hurt

Gandi has been working well for me. It just chugs along. Good UI. Doesn't try to upsell me anything or be my friend. All the mails I received in 5+ years were purely transactional: payments and notifications for expiring domains where I don't have auto-renewal enabled.

Surely that is true for other registrars as well, but I've had no reason to look further.

I've found the dev experience with nuxt to be more enjoyable overall than it is with vue-cli. The main reason for that I would say is that you don't have to bother with routes and the generator can set up Tailwind (or other CSS frameworks/tools)

Generally, it feels like it strikes a good balance between being fully configurable boilerplate and opinionated framework.

SEEKING WORK | Germany, REMOTE PREFERRED | Short term / part time Experience with: Javascript, Frontend, Elixir, DB, Crypto

Preferred work is early stage development: RnD/Evaluation, Prototyping, Scaffolding, MVP

Detailed experiences:

- Vue.js interfaces and backend integration

- Node backends - Express, Koa, Knex

- Elixir backend and tooling - Mix, Phoenix

- Databases - Redis, Postgres, MySQL

- PostCSS / Tailwind

- Object serialization - Protobuf, MsgPack, Schemapack

- Interactive chat bots and tooling - Telegram

- Crypto / Blockchain / DAG - IOTA

Email: ml@nullpilot.de

SEEKING WORK | Germany, REMOTE PREFERRED | Short term / part time

Experience with: Javascript, Frontend, Crypto, DB

Preferred work is early stage development: RnD, Prototyping, Scaffolding, MVP

More specific experiences:

- Vue.js interfaces and backend integration

- Node backends - Express, Koa, Knex

- Elixir backend and tooling - Mix, Phoenix

- Databases - Redis, Postgres

- Object serialization - Protobuf, MsgPack, Schemapack

- Interactive chat bots and tooling - Telegram

- Crypto / Blockchain / DAG - IOTA

If interested, my email address is in my profile

Not OP but yes, absolutely. JSON and MsgPack are schemaless, which means they put the schema, including object keys etc on the wire. On every transfer.

The problem is less the client, you're right with that. The problem is that server bandwidth and CPU scale up really quickly if you try to do 30fps, no matter what method you use to keep state in sync. If you want any significant amount of players in a realtime game, this will be one of your first bottlenecks, probably before any encoding and decoding.

For less realtime-y games, JSON and also socket.io can be perfectly adequate.

Protobuf is just insanely slow to encode/decode client side. So that's out too if you want fast paced games. And for slower games it is not worth the effort.

Messagepack still contains field names as strings, which can easily double or triple your data, and explodes parsing time.

A game is a pretty good use case for predefined schemas like Protocol Buffers, which is used by CS:GO and Pokemon Go for example. Other games like slither.io use binary over websockets without any of these libs.