They are common features on a smartphone. This is an AI device that is not positioned to replace your smartphone.
I was not interested in alarms and timers (my phone already has them) but I like how the Rabbit team made them smart. This is now the only device I know of on which you can set a timer for a complex indirectly defined time period. Eg “Set a timer for boiling an egg at 2000 meters altitude.” Try that with Alexa. Or ChatGPT 
I think you’re not wrong, but now imagine it realistically, OK? What state would you say r1 is in now? For my part, I’ll say it clearly, I think what the Rabbit team has done so far is really great and r1 is already worth more to me than the $200 I invested, as it is, but there are still a lot of bugs and at least as many improvements are due, which should come at some point. But the bugs are probably exactly the problem in this point that you are addressing here. There are still a lot of bugs and just imagine that it is not easy to fix these bugs, especially when there is a small Rabbit team that has its head full of work and so many things that still need to be done and that in a certain series and from the community there are more and more requests. I think that alone is a huge point, but if all kinds of languages were added, I’m sure that the bugs would be almost impossible to fix or would only be possible under very difficult conditions. So I can understand that this issue with the languages could drag on for a long time, in the worst case until the rest of the software runs without problems. But that would be completely fine for me, because I would understand if that really were the reason. I just think, thank you, dear people in charge and developers of Rabbit, for what we are already able to hold in our hands today, you are great and please keep up the good work. Thank you @rabbit !
its free to think! thanks, i stand with my opinion, i hear yours also is ok. i was addressing this to the @rabbit team so i will let the judge
keep the peace!
Oh, I know this. But I also see the team already addressed this request in the past and mentioned they will fix it or add a feature for our r1 to remember if we want Celsius/Metric instead of Fahrenheit/Imperial so I’ll wait for them to be able to add it and in the meantime there’s a workaround that works fine.
24h clock setting is quite common on digital clocks. Don’t get why people argue r1 doesn’t “replace our phones”, r1 barely does anything smartphones can’t. So everything we do on r1 is something we could have done on our phones, so we’re using r1 instead of phones? Sorta like it replaced the phone? And yes smart alarms are good, but any alarm or timer functionality in the past 3 months would have been nice too.
I think Apple also does this 9 minute snooze timer (and many others), and I believe from what I remember reading a while ago once, it’s an ode to the old wind up alarm clocks that the coil winding would max out the snooze when you wound the crank in the back to 9 minutes for a snooze due to mechanical limitations.
Hey guys, unfortunately I don’t have anything for you that you could win with a bit of luck, but I would still like to ask you all, if it’s not too much to ask, to vote quickly.
But you could still win something this way, namely valuable knowledge, and that is worth something after all too.
Thank you very much to everyone who votes!
Imo, the purpose of the R1 is to intelligently integrate across channels and devices using a voice first interface. So my smartphone would be a backend device, the apps on it would act as services for the R1 to use to achieve a goal (so that I don’t have to juggle all those apps to get stuff done).
I totally agree that it is nowhere near delivering on this purpose but any feature that does not bring it closer to that purpose would, imo, waste valuable time (unless required to keep users on board / happy). I’m not saying that the 24H clock was purposefully deprioritized to allow working on more urgent features but I do know that the first users were all US users and they would not have cared about a 24H clock.
For me, I would be fine if it would not show the time at all; I have more than enough clocks around me all day.
I’m curious; is your opinion that you believe priorities for features in releases should be / should have been different, the speed of development is too low or that the device should have been released later, as a more polished product (or something else)?
I mentioned it also before, i do think that outside US users are forgotten a little, or a little more. I see people throwing the 200 bucks like is an excuse for not having some basic futures that are important for users that dont use the standard from the device, in the end i think is about offering your user a fair use of the device. Starting from the units thing till having functionality with equivalent apps from the other regions, as some apps their promised we all can use are not available in this regions like dash and uber.
i consider this not negative comments, as much as how important is for users in this region of having a fair use of the device. other regions where even at delivery in my opinion “forgotten” in a way for having to wait longer than promise, i was in batch one and i thought is fair they would ship it in the same time, of course i have to consider their logistics and to understand which i did. after arriving so many dis-considerations for the outside US users.
I dont want to get miss understood, i like the product and the idea and still hoping it will at least get to the state of how it was sold to us. thats the only expectation i have from the r1 team, and as well i dont think is much to ask from to fix a major “regional” update.
we where told just ask the weather in C and it will tell you, but why not the other way around , the r1 to ask perplexity or whatever he uses for weather information, the weather according to user preferences that dont need to be mentioned each time. then it can offer the proper answer… in the end r1 is the AI and can automate some little things not the other way around. right?
I don’t have a view on the team’s backlog but hearing the product vision the team is working on personalization settings. I’d be happy to wait a bit longer if these settings turn out to be flexible enough not only to fix my preferred units and other localization settings but also that I don’t own a car, that I’m a vegetarian, that I like British humor, prefer beer over wine and that I have kids aged 6 and 4 (just to name a few random factors that will improve interaction relevance).
I’ll be clear, the main problem I see here is that @rabbit obviously can’t set the right priorities to develop basic things in detail so that they work completely bug-free.
But that’s also because, due to the enormous pressure they’re under now, they probably feel compelled to deliberately set the wrong priorities, just to keep people on the same page.
In that point, I agree with @PaulBacon and many others here that r1 already has features that are actually superfluous for such a device.
Of course it’s nice to have them and they could of course always be better, but from my point of view, Rabbit can’t really do much to stop things from running the way they do.
They just always seem to try to operate the valves that put the most pressure on things as quickly as possible and the result is generally more or les good, but apparently not always that good.
It gives me the impression that they’re always trying to put out fires, which is completely understandable.
Many users are simply dissatisfied and put pressure on them, I can understand that, but it’s not good, because I think that if the developers at Rabbit had the chance to get the basics right without errors, then the quality of the other things that still need to be implemented would be much better than it is now.
Disadvantage: r1 could do much less than it does now, but what it could do would really be 100% good.
So, take a look at the usability of r1, I think it could be made much better and really intuitive, so intuitive that any child could use it without ever needing instructions.
But that’s not possible if you constantly have to program an all-rounder to put down the pressure that is on them.
So I see that as something that Rabbit simply cannot do otherwise.
At least that’s the case if you try to put yourself in the other person’s shoes.
I mean, hey, they had a really cool idea with the r1 and sold it all over the world.
And yes, they probably encountered unforeseeable problems, as is often the case when you develop software, probably also in connection with the fact that they sold the r1 all over the world.
Then there was all the pressure from the community and YouTube and so on.
What should they do differently?
They can’t do anything else?
But it would be much better if they could just put everything aside without pressure in order to do the really important things first.
And that’s exactly why I always preach here…
I understand everyone who is dissatisfied, but I think it’s important to see exactly why you’re dissatisfied and to recognize your priorities.
And like me now after this story with the Morse codes, to point out the problems that have arisen, maybe also with humor (like me), but still try not to put pressure on Rabbit and just make the best of it.
Simply use R1 for what you can use it for today.
Although you now have to be a trained Morse code specialist to use r1. (Whose idea was it? *lol)
With that in mind.
can I ask u, did you got hired as a lawyer or something ? or at least a social media job … or are you just an activist? im done with you answering everything and defending like a loyal DOG something that can be rational … amin !
god bless america then!`
i almost feel that this is actually a contra offense from rabbit team to cut down logical questions that user are having …
paece and love mate ! keep the peace , and don’t forget all as one, or all for nothing
I wasn’t trying to express any opinions like those. I just said that it’s not wrong or unreasonable for people to have complaints and criticisms about this development process, and that turned into a big argument with multiple people.
This is the best part of the update, You have been listening to us! Looking forward to seeing all of the future updates and projects. I know YouTube has been bashing r1 and Facebook has too. We have to show them they are wrong but don’t focus on them or the competition, stay focused on the dream team. As Jeff Bezos says never get past day 1!
The PTT 8x power off was a great update! Because before if your query was long it would simply power off before you finished talking.
The 8x PTT is a mistake in my opinion, there are much better and more intuitive solutions. Having to press a button 8 times shortens the lifespan of the button and is not intuitive at all, it basically completely contradicts the basic idea of r1 and is therefore unfortunately to be seen as a misdevelopment.
Even more misdevelopments like this and in the end no one will be able to remember how often you have to press the PTT button for what, in which case, the result of this will be that users will do things they don’t want to and won’t be able to do things they actually wanted to, at least not straight away.
The rest of the updates are really great though, thank you very much. @rabbit.
In the end, it will also lead to your r1 being a bigger time waster than your smartphone and I think that is something that completely contradicts the basic idea of r1.
Completely intuitive usability is therefore the most important thing and having to press a button X number of times for different functions in different cases is definitely not intuitive.
Please read this! Thank you!
Literally called r1 one the greatest devices ever…hounded me for a day because I dared to suggest it’s not perfect…now saying the device is ruined because we have to press the button a few times in a row.
I think we’re at risk of going in circles here now.
@RaRa It was not my intention to be reductive in regards to your post, and I apologise if it came across that way.
It’s my job to make sure we’re a community centric company, so when I see a suggestion that we aren’t listening to feedback, it just makes me a bit sad, because I know that we do and have worked hard to create great systems that allow us to do that.
Of course, how that looks to the end user is a variable scale, there are things that we want to do that the community wants which simply aren’t feasible just yet with the resource that we have. Equally, there are things that have been fixed or implemented or placed on higher priority because of what we hear from users.