it is true that iphones itself isn't a monopoly (yet), but i reckon consumer protection should extend to the ability to install arbitrary software on a device they purchased, regardless of the intent of the company selling the device.
This argument doesn’t hold now that Firefox’s smaller and less funded competition manages to deliver. Being forced to use a webview does not leave you as helpless to implement features as Mozilla stans claim.
being able to block ads, vs being able to install extensions, are two separate requirements with different difficulties. In the past, apple was anti-extensions - your app weren't allowed to be able to load remote (and thus unreviewed) extensions that executed code and changed app behaviour.
Thanks for the kind words! As I briefly mention in my video, my teammate actually had guitar tabs going, with lyrics chords and even web scraping/search. I think a bit of refinement and better hardware and we'll get what you're looking for
Agreed! These glasses do look very normal - only tell is that at a certain angle you can see the green of the screen, and the part near the ear is a bit bigger (but easy to conceal with hair)
This would make the most sense, since MuseScore is notoriously litigious about usage and redistribution of their library/MusicXMLs, so a collaboration would be necessary to get a usable music catalog for smart glasses
Yeah, it's a big deal for sure, I was bugging Mentra all hackathon to try and lower it, and also reached out to Even for suggestions (which Mentra is implementing). Regardless, I made it work and next gen hardware, firmware and software are all definitely going to be better for bitmaps
If they're using the same Nordic BLE chips everybody else is, there's just gonna be a cap on how quickly you can move stuff, I think.
I've found the display capabilities of the current gen smartglasses pretty disappointing. Yes they're less obtrusive, but the resolution is pitiful. I've found the Vufine a lot more useful, if more ridiculous looking.
The Nordic MCU they use isn't actually the limiting factor, rather it's the glasses' firmware. For bitmaps from third party apps (like AugmentOS), they enforce 194 byte chunk sizes and do not support RLE. Their first-party app does not have these limitations. We're stuck with this problem for the G1, but we're working with hardware partners to make sure future glasses don't have these issues.
If I were designing around this limit, I would put enough memory to be able to store a nice buffer of bitmaps in either direction and then do sends that don't change what's currently displayed. I feel like that memory probably exists, I just don't have access to the firmware sadly
Seems cool! Thanks for sharing. Even though it's MIT licensed it's written in Java, so unfortunately I can't borrow any code, but it's nice for inspiration.
For me, it's still easy to mess up for complex sections if I'm not peeking at the keyboard every so often. Its true that muscle memory takes over after you reach a level of familiarity but not quite to the extent of biking
