After all these, I still feel their voice AI interrupts quite a lot, especially when I pause just for 0.5 sec. Interestingly, when I tell it to interrupt less, it seems to be better.
off topic but I just wonder if this page is AI-designed. It looks quite good to my eyes. I feel like prior to coding agents this would instead be a blog post with some charts.
I'm building Eima (https://eima.app) which combines your Todo List and Calendar, allowing you to schedule your todos by simply dragging them onto the calendar.
Similar apps have existed before (like Amie), but they were nearly all VC-backed and had pretty much all pivoted to AI (e.g. being an AI note taker). Their approaches to a Todo-focused calendar has been largely unsatisfying due to the focus on Enterprise users and whatever is trendy.
Eima, in contrast, focuses on personal use and does one thing very well: scheduling your todos. In particular, I spent a lot of time making sure multi-occurrence todos work smoothly (e.g. todos that need multiple attempts or simply recurring todos). These were not addressed by prior tools at all and had been my biggest motivation to build Eima.
Would love some test users! If you end up wanting to give Eima a try please use the code EARLYEIMA to get it for free.
I'm honestly surprised by so much hate. IMHO it's more important to look at 1) the progress we've made + what this can potentially do in 5 years and 2) how much it's already helping people write code than dismissing it based on its current state.
I think one rule around Show HN is that you allow people to see content without signing up, let alone paying for it. So this is a violation of that rule.
Edit: actually search is not behind the paywall (although that's not very obvious)
couldn't take this article seriously considering it doesn't mention Meta's Rayban smart glasses, which largely does what they want already: a pair of glasses without visuals but with AI in your ears
This has been a great idea for decades. I want Haystack to be successful just like many other attempts. The early execution seems promising. And I suspect there will be many challenges (e.g. when it's hard to figure out caller/callee,, inconsistent UX preferences across developers, etc). Kudos for taking this on!
Btw I've always thought that this is even more powerful when the screen estate is more infinite than a 2D screen (like in a VR headset).
In a project my questions are usually revolved around the same topic. Having context carried across threads actually make a lot of sense.
In the general mode where I'm expecting models to be *stateless*, having memory is very annoying.