This one is more of a question to LaForge themselves since I'm not sure if anyone has received a shipment yet and hopefully Corey or someone can step in and answer this one. I was curious as to how long it takes for notification such as a text message to pop up on the eye wear? Is there a long delay between reception of the message and the message coming up on your POV?
I mainly ask because I have a very close friend of mine who was born physically mute and was wondering if Shima would lend me a hand at communicating with them if they would be able to text me and bam! its right there in front of me without having to look down on my phone. (No I don't know sign language, we only communicate electronically through texts/emails for the time being. They live far away.)
Also having different Profiles of settings you can select at a tap or two, such as "Running/Exercise", "Driving", "Leisure", etc. that override the speed based mode changes.
That's what I am hoping for as well, and am expecting to see. The customization to set what apps are displayed or restricted depending on which mode the glasses are in. Quite a few people carpool or commute on public transportation, and it wouldn't make sense to limit their options.
If I understand correctly, the default change to notifications in drive mode will be the shortening of full notifications (I.E. a preview of a text) to just an icon with a number in the corner showing how many there are.
I'm intentionally holding back from getting too many details from the rest of the team so I can experience the Alpha and Beta alongside the rest of you; if I don't have an answer to any specific question, it's because I'm leaving it for Corey or another to answer. =)
Also what if I am a passenger in a car? Am I not able to use my glasses? Have a one time ask pop up if you are a passenger of a car because I hate being a passenger and an app keeps asking me every 2 mins if I'm still the passenger.
It should not be disabled in drive mode. That was one of the big things for smart watches. Receive a text, be able to interact with it and reply hands free. Wrist gestures and voice activation made it legal to be used. It's up to the driver to be responsible with this interaction, just like it would be for any interaction with a car hud or even looking down to the radio.
You're right Adam. I forgot about the DNA feature automatically switching.
Isn't text disabled on the Shima while moving at driving speed...? I thought it would be Navigation only?
The "missing texts sent quickly one after the other" problem likely stems from your phone grouping those texts together into a single notification, and your car doesn't know what to do with that. This shouldn't be a problem with a display interface, and we'll definitely find and fix it during Alpha testing if it is!
Thanks for the input!
Thank you Josh for your reply. Its a nice timing I would have to say. I asked only because my car has one of those built in Blue tooth text voice readers that most new cars come out with nowadays. The delays on my vehicle's blue tooth device can be a little slower than preferable or will sometimes miss one notification of a text message if they were sent one after another in 2's or 3's. It's also not the safest thing to play with while driving. Shima is gonna make things much more fun, convenient and even safer I believe while driving.
It's a valid question, and I'm happy to answer. As with any other Bluetooth peripheral designed to play sound or display notifications: the delay will normally be between under a second and a few seconds (depending on your model of phone) provided you have both devices powered on, Bluetooth enabled, and Do-Not-Disturb disabled.
Notifications are extremely short data files, and Low Power Ultra High Frequency radiowave transmission protocols like Bluetooth are designed to send data near instantaneously. The only things that factor into slowing down your notifications is your phone's processor and available RAM, and human error.
Hope this helps!