isn't a similar thing done by entire cli? the startup which raised $60M seed recently

same thought, we've been using smartphones since 2 decades now, and not just we dont have a problem with qwerty, but anything new will be requiring more cycles to get accustomed to

I can touch-type with flow typing in GBoard at this point.

That's to say, I'm writing this comment on my Android phone without looking at the keyboard.

QWERTY is in my muscle memory in such a way that words have become writable as single stroke characters.

I really, really doubt this Keybee thing can be an improvement over that in any way.

I really want to see the visualization of words as the swipe typing patterns. I tried doing it on paper and realized I couldn't understand it just by looking but once I started visualizing it and swiping in my head I could start to get a feel for it. The tricky part is figuring out where in the keyboard the stroke begins

I also would like to implement all those texting algorithms but I need the help of the open source community at this moment. Cheers!.

People riding horse buggies probably thought the same when powered vehicles first came about, and look at the world now. You won't know unless you give it a honest try.

QWERTY won't be replaced on phones until there is a full phase change in how people interact with their phones that absolves us of keyboards entirely. Anybody here who thinks otherwise is welcome to make an offer to buy my two decades of notes on the topic.

>People riding horse buggies probably thought the same when powered vehicles first came about, and look at the world now. You won't know unless you give it a honest try.

This is a ridiculous non-analogy.

I'm flying a jet airplane, and you're telling me to give Ford Model T a try because you don't understand flight as a concept.

Or, in this case, Flow typing.

From Keybee's website:

>Some syllables and some words can be inserted through a simple combination of tap & swipe (we call it twipe) greatly reducing the number of touches for typing a text. For now the twipe is limited to the adjacent keys. Keybee Keyboard is swipe friendly.

I am typing an entire word with one "twipe" on GBoard.

Each word.

I'm done with touchscreen input methods that require me to think about tapping letters. I don't think in individual characters, and I don't type in them either.

Let me know if I can make it any clearer.

Also gboard is the best keyboard for that. Nothing else implements a prediction model over a number of words as far as I can tell. Or if they do, they fail really badly at it.

Swipe keyboard on Microsoft Lumias was better.

I think Android is only catching up to it in the past 2-3 years.

Sadly, Lumias went the way of the dodo, and I don't have a need for that sort of input on something that's not a phone.

Whatever Microsoft put out as a keyboard app for Android is different, they didn't implement the same UX.

Out of the swipe keyboards I tried for Android, GBoard worked the best.

Weird thing to say, why would a random port be peak efficiency that can’t be improved?

awesome, does it also show if its stuck somewhere like auth or requires human in the loop?

meanwhile me adding to the .md file, "you're not a LLM and instead a super intelligent agent to help me find HN trends"

I've been trying to avoid this since 2022 (wish i knew this before that), def concerning how coffee shops still encourage this, we need a new revolution for something which can make cups for one time use but also not toxic like plastic

Nice, for data is there an available API out there?

Some thoughts on a simple UI fix, show readme on top. Possible opportinuty to make it default and customizable both

I've seen hugh abroad's videos and they are genuinely interesting as he explores south asia. Overall there's an interest element since people in west are accustomed to a baseline luxury and when they try difficult things like "walking in peak chaos while trying spicy food", it gathers attention from the same countries which represent almost ~25% of world population

You just earned yourself a customer. I love simple apps like this. And anything which can help to reduce friction here can be translated to a DAW and added effects for a real production

Thank you so much! That workflow—starting with low friction in the browser and moving to a DAW for the final polish—is exactly what I'm aiming for.

I'm actually thinking about adding a MIDI Export feature soon, so you could sketch a quick beat here and then drag the pattern directly into Ableton or FL Studio. Would that fit your workflow?

Great idea overall. I'm sure you'll reach 100 users soon (android user here) Do you index all repos in a cadence and then let users swipe from a pool, or is it real time GitHub api calling?

Thank you. The app has two sections: curated and trending. Curated repositories are prefetched and stored in the database. Trending repositories are fetched daily via the GitHub Search API and subsequently stored. This process enriches the repository pool and allows the backend to index each repo. Whenever a user interacts with a repository (star or pass), the action is saved; this ensures the same repository is not displayed twice.

This is cool! looking forward to the android app