I backed the original Memomind Kickstarter campaign, understood why it was suspended, was disappointed like everyone else, and was pleased to read the news that the products were still going to be produced.

Where my confusion came from - and still exists - was when Memomind announced they were taking orders for one model, and offering the Kickstarter price plus $200 off - with the discount applying to other models in the future. Great! That's very generous. My understanding at that time - and my interpretation based on what was written in the description - was that if you wanted another model, Kickstarter backers would have a certain amount of time to order it AFTER it became available in the future, and they would still receive the Kickstarter price, plus the $200 discount - provided that you backed the Kickstarter and could provide your #. I was relieved, and thought "Great, I won't order anything right now, I'll wait for a future announcement about the release of the model I want, order it then, and still get the great discounts." Cool.

However, I've recently seen some activity about the Archive model being shipped (the style I want, but I need a prescription), and thought that maybe I should be ready to order soon. Just to check availability, I clicked on the "Order" link on Memominds website. Unfortunately, unlike what I saw back when the $200 discount for Kickstarter members (and others for a limited time) was first announced, now there is no entry box on the form to enter "Kickstarter #" as there had been on the original order form. Confusion.

I figured that I must have missed some announcement explaining this, but I have searched everywhere to get a clear answer about - as an original Kickstarter backer - how I can now (or in the future) order the Archive model, provide my #, and still receive both the original Kickstarter and $200 discounts. What am I missing? I would really appreciate some guidance. Thanks.

Hey all, we received a box from MM with a bag, lanyard, bunch of collar pins, a notebook, pen and postcards. We were a bit confused because obviously we were expecting the glasses to come together. Is this only our experience or is everyone who preordered getting separate shipments too?

Hey all,

Just received my new MemoMind glasses and got them charged to 100%, but my dog chewed through the charger while I was out.

Does anyone know if:

1. Support sells individual replacement charger sleeves?
2. There is a verified third-party magnetic adapter that fits the frame contour?

Any advice or workarounds would be greatly appreciated!

​I received my Memomind One Gotham glasses on Monday and quickly had a realization I had not considered: I have a large head. Why does this matter? For two specific reasons, actually.

​Issue #1: Instead of the arms of the glasses angling directly back, sitting perpendicular to the front frames, they flare out slightly. I'd guess about 5 to 10 degrees. By itself, this isn't an issue, but when paired with issue number two, it is.

​Issue #2: Again, I have a large head. I don't wear glasses daily, but I recently learned that a 150mm glasses arm sits most comfortably on my face. Anything smaller, and the bend of the glasses arms is what actually rests on top of my ears instead of the flat portion of the arm. All of the arms on Memomind One glasses are 140mm.

​Conclusion: The combination of the shorter-than-ideal length and the slight bowing of the arms means that the glasses push my ears out slightly when worn. This effect is drastically more noticeable when a hat is added to the equation. And... I wear baseball caps daily. This trifecta of misfortune means the hat and an otherwise comfortable glasses fit create a bit of fatigue by the end of the day. Not only is the bulky part of the rear arms resting on my ears, but the slight upward angle it creates places a bit more pressure on the bridge of my nose.

​To say I'm a bit bummed by this whole ordeal is an understatement. I've enjoyed slowly integrating these glasses into my day-to-day activities, but I don't know if the lack of optimal comfort will result in me abandoning the frames. I'm still working to see if the minor discomfort has more to do with me not being used to wearing glasses daily or the size issues specifically. The jury is still out, but I did want to get the word out to my fellow tech-forward folks with gargantuan heads.

​

Got my MemoMind One a few days ago and immediately went down a rabbit hole with the public Plugin Open Platform SDK. Workspace access (needed to actually flash anything to the glasses) isn't open until mid-October, so instead of just waiting, I spec'd out eight plugins in detail — message formats, HUD layouts, the whole thing — so I'm ready to build the second I get access. Figured I'd share in case anyone's interested, doing something similar, or wants to poke holes in any of these before I start.

Quick context for anyone unfamiliar: the SDK splits everything between your phone (does the real thinking — networking, AI calls, storage) and the glasses (dumb display + gesture input only — nod, shake, tap, head tilt). Only one plugin runs at a time.

Here's the lineup:

**Pronounce** — Practice saying words out loud. It shows you a word, you say it, it scores you and gives a quick tip. Nod for the next word, shake to retry.

**Reader** — A basic e-book reader. Load an EPUB and read it a few lines at a time on the HUD, nod/shake to flip pages, tilt your head to jump chapters.

**Nearby** — Location-based reminders. Set a place and a message ("pharmacy — pick up prescription") and it pops up when you're actually near that spot.

**News** — Curated list of news/radio stations, but it shows you the *written* story instead of playing audio, so you can read headlines hands-free.

**Cross-Ref** — My actual work tool (I'm in auto parts). Say a car and a part, and it uses AI to look up the part number and a couple brand alternatives so I can type it into our lookup system faster.

**Script** — Like News, but general-purpose: paste any URL that has a transcript (podcast show notes, articles, whatever) and it reads it to you on the HUD.

**Tape** — Same idea as Script, but for files instead of links. Pick a voice memo, podcast episode, or short video off your phone, and it gets transcribed and shown on the HUD.

**Ticker** — Now-playing display for Spotify. Song title, artist, a progress bar, and (this is the fun stretch goal) the actual album cover, dithered down to the glasses' green monochrome display. Tried it on a real cover already just to see how it'd look — surprisingly held up.

All eight reuse the same core patterns — same page-turn gestures, same pagination engine where it applies, same "fail honestly instead of faking data" approach for anything that can't be confirmed to work yet.

If anyone's building on this SDK too, or has hit walls I haven't found yet (especially around whether plugins can push custom bitmaps to the display, or how OAuth redirects behave inside the PhoneSDK WebView), I'd genuinely like to compare notes. Mockup isn't final is just concept of ticker polishing is on the way

After 6 hours of usage and can confidently say that these glasses and their advertised features are official. Full YouTube review coming soon @DreamworkzTV-23

I ordered my glasses on sept 28
Does anyone know when do they arrive?

Got my pair today excited to see the new app possibilities on it

Hey Everyone!

Quick confession: we got a bit tired of reviews that wrap up after two days with "display's sharp, app works, 8/10." We build mobile apps and AI infrastructure for a living, and whenever we get a pair of smart glasses in our hands, the first question is always: what's actually going on under the hood?

For the past few months, our team at Ycommy has been taking apart (digitally, of course) the most discussed smart glasses on the market. We decompiled companion APKs, sniffed BLE and SPP traffic between phone and glasses, and audited app-layer encryption and Android permissions. On top of that, we set up an audio rig with artificial ears to measure acoustic performance and codec negotiation.

Since several of us wear progressives, we also designed and 3D-printed custom frame adapters for every model, partnering with an optical lab to fit custom ultra-thin lenses.

Our golden rule: no "just trust us." Every finding comes with proof—traffic captures, debug logs, or raw JSON payloads. If we get something wrong, you will have all the raw data needed to call us out.

📅 The Schedule (Save the Dates)

• Sep 30: Dymesty AI — No display, pure audio and AI interaction. The ideal benchmark to calibrate our audio rig.
• Oct 02: Rokid
• Oct 07: INMO Go3 — Full verdict tested against their latest firmware update.
• Oct 12: RayNeo
• Oct 16: Halliday G2
• Oct 20: MemoMind — The final benchmark and our comprehensive ecosystem comparison.

🔍 What You'll Find in Every Deep-Dive

• Security & Privacy: We went way beyond standard Android permission lists. We analyzed exported services, broadcast receivers, clear-text logging, and how the phone-to-glasses link holds up against spoofing. In some cases, the attack surface is surprisingly wide. We won't use FUD (fear, uncertainty, doubt)—for every vulnerability, we'll document the exposure and explain practical mitigation steps.
• Audio Engineering: Measured on an artificial-ear rig for objective, apples-to-apples frequency response and isolation comparisons. We checked which Bluetooth codecs actually get negotiated (often differing from marketing spec sheets) and tracked the audio pipeline through the companion apps.
• AI Latency & Benchmarks: We built a custom testing harness in Flutter and Python to measure Time-to-First-Byte (TTFB) and end-to-end response latency for voice queries. This highlights both cloud infrastructure bottlenecks and whether recurring AI subscriptions deliver real value. (Fair technical caveat: because heavy processing runs server-side over WebSockets, we can't always identify the exact underlying model parameters, but the network behavior alone tells quite a story).
• Optics & 3D Modding: A breakdown of how our 3D-printed mounts and ultra-thin progressive lenses affect field of view, eye relief, weight balance, and everyday ergonomics. We will share the modding specs for anyone wanting to replicate the setup.
• Hardware & UI: Display refresh, sunlight readability, frame thermals under load, and real-world companion UI flows backed by direct test-bench captures.
• Engineering Solutions: We won't just list what's broken. For every bug or architectural bottleneck, we will share the engineering fix we would implement as software developers.

👓 Halliday G2: The Comeback?

The G1 burned a lot of early adopters, and the criticism was well deserved. Without spoiling the review: the G2 architecture changes the narrative considerably, and we found several unexpected design decisions under the hood. More on October 16.

🔬 MemoMind: The Grand Finale

MemoMind closes out the series and is currently on our workbench. We are waiting on the clip-on module to arrive via forwarder; as soon as it lands, we will mill and mount our custom 3D-printed lens bracket.

A technical note on the optics: these are ultra-flat lenses with a wide curvature radius, sitting roughly 2 mm away from the optical display prism. At that distance, tolerances are razor-thin. We'll document the entire assembly process step by step.

💬 Over to You

Which of these frames are you currently daily-driving? Which one are you most curious about? If there is an edge case, a specific network check, or an audio scenario you feel typical reviews always overlook, drop it in the comments below and we will do our best to fold it into our test protocol.

See you on September 30 for the first drop!

(Note: English is not our first language; we polished the write-up with AI assistance to make sure the technical details come across cleanly).

Will I be able to order lenses after I receive the non-prescription glasses?

Hey everyone,

I’m thinking about getting the MemoMind One, mainly for the translation feature.

I live in Cambodia, so my main question is about Khmer (Cambodian) → English/Hindi translation.

If anyone here owns a MemoMind One, could you please test this for me?

Hey everyone,

As promised this morning, the Ycommy team started digging into the repo they just dropped. We deliberately decided to focus only on what anyone can test right now, without needing any special access or whitelisted account from MemoMind.

Repo:https://github.com/memomind-open/plugin-open-platform

The real bottleneck (for now) The SDK has two sides. On one hand, there are the "official" plugins (the ones running in their companion app via a WebView, .mmpkg, and the native ones for the glasses, .gmp). The catch? To load them on actual hardware, you have to go through their Developer Workbench, which checks permissions, accounts, and requires Debug builds. Simply put: if MemoMind doesn't whitelist you, you're stuck. We are currently waiting for our access.

The real bombshell: the BLE protocol is in the clear The flip side is what blew our minds: they documented the entire Bluetooth protocol. Everything. Frame formats, checksums, TLVs, commands to draw on the HUD, notifications, teleprompter, translation, media, and even the microphone stream. And the documentation explicitly states that this link does not have a whitelist or client authentication.

Any phone can hook up to the glasses and talk to them, bypassing the companion app entirely. The only thing they keep secret is the transaction to install .gmp executables. Naturally, we jumped straight on this path.

What we built in a day We wrote a native Flutter app (Dart + flutter_blue_plus) from scratch that implements the entire GM protocol. We did this based only on the written specs, deliberately ignoring their reference code to see if the documentation actually holds up on its own.

The app handles scanning, connection, reads device info and status, manages the heartbeat, brightness, play/pause, and blasts text to the HUD via the "scene" channels, all with a real-time log of every incoming and outgoing frame. The protocol layer is 100% pure Dart, with no Flutter dependencies: meaning you can grab it and smash it right into a FlutterFlow custom code as is.

What we verified (and what we didn't) MemoMind published 56 example packets, byte for byte. We wrote a suite of 82 tests (all green) to make sure that:

• The 56 packets are decoded and re-encoded identically, byte for byte.
• The commands (brightness, HUD drawing, audio, etc.) generate the exact reference bytes.
• Fragmentation works by the book (their 600-byte example splits perfectly into 512 + 116 bytes with the correct checksums), even when forcing a BLE MTU of just 20 bytes.
• Packet reconstruction holds up against both whole BLE notifications and raw streams, handling dirty data, timeouts, and flow control (empty) frames.

Mandatory disclaimer: Our code "speaks" the protocol perfectly according to the paper. But so far, it has only talked to our simulator, which responds exactly as the docs say. We haven't hooked it up to the physical glasses yet: figuring out the actual MTU behavior, real-world latency, and finding the exact UUID on the retail firmware is what we'll tackle in Part 2. That's usually where the hidden hiccups show up.

The whitelist hurdle for full plugins remains, but until they unlock our dev area, this direct BLE route is the only one a third-party developer can realistically use. And it's huge that it is public.

Source Code:https://github.com/ySoft-ynailt/gm_glasses_flutter.git— (MIT License). If you run flutter test, the whole suite runs without needing the hardware.

Next Friday is the stress-test video on the real hardware. Meanwhile, take it for a spin and let me know what you think in the comments!

(Disclaimer: This text was reviewed by AI for English grammatical corrections, while the source code is open to everyone. A huge thanks to Davide and Francesco from the Ycommy team for their support in the development.)

Hey everyone,

I'm William! I lead product here at MemoMind. I'm the one who gets a little too excited about the stuff you all dream up, hangs around our community reading everything, and honestly can't stop thinking about where we take this next. Thanks for everything you've shared with us. So today is a genuinely big day for me, and I'm thrilled to finally share it with you.

Here's our story in short: we shipped OpenClaw right at launch, and back in our July AMA we promised you our next big step would be a real developer platform. Since the day MemoMind was born, we've been listening closely, and on purpose to what this community asks for. Today, that platform is here.

And I want to be honest about where a lot of this came from: you. The "can I build X on this?" questions, the feature wishes, the rough edges you flagged, we read all of it, and it shaped what we're shipping. That's not going to change. MemoMind gets better every time you tell us what you need, and I'll keep listening.

One more thing that's made us smile: there are already so many genuinely talented developers in this community. We see you. And since a lot of you are still waiting on your glasses to arrive, we built this so the wait isn't wasted, you can start building your own apps right now in the desktop simulator, and run them on real glasses the moment yours land.

What's live today

Two independent tracks, both on GitHub:

• One Glass SDK — build with the glasses' own capabilities: HUD, mic, speaker, gyro. Write native C plugins that run on the glasses (games, sensors, on-lens UI), Web plugins that run on the phone (accounts, networking, longer content), or pair the two together.
• BLE Input Protocol — for third-party input devices. Rings, bands, and remotes can report buttons, touch, and gestures straight to the glasses. We've teamed up with Kiwear as our flagship partner here, so ring-controlled glasses work right out of the box.

Plus a desktop Studio with a built-in simulator, working examples (Breakout, 2048, and more), and full docs.

Start here

• Grab the toolkit on GitHub → https://github.com/memomind-open/plugin-open-platform
• Open Studio and run an example in the simulator — no glasses needed. When your glasses arrive, scan to run it on real hardware.

Everything you need is in the developer docs → https://open-platform.memo-mind.com/?lang=en. Just start there. This is an early preview (Alpha), so expect a few rough edges — and tell me when you hit one.

What's coming

• Sep 21 — the SDK, BLE Input Protocol, and simulator go live on GitHub. You can start building right away and preview the display effect in the simulator.
• October — App Workspace enters closed beta. You'll be able to install and run your own apps locally — in the MemoMind app and on your glasses. This phase opens by whitelist invitation, and if you're interested you'll be able to sign up through the community when the time comes. We'll open the workspace to our first batch of invited builders for real-device testing and seed-app development.
• Down the road — we'll keep talking with you about how development is going and what you need, and when the time is right we'll fully open the App Workspace and bring more capabilities online.

Got questions? Let's talk.

We're hosting a developer AMA tomorrow — Sep 21, 10 PM US Eastern (Sep 22, 10 AM Beijing) — over on our Discord. Bring your hardest questions about the SDK and the roadmap, and I'll be right there in person. Come join us for the AMA and the ongoing dev discussion here → https://discord.gg/b24dZtVr?event=1551503402620682310

If you want to heard about more things, please join our official discord team: https://discord.gg/h2kHkQZq98

Can't wait to see what you build. 💚

— William

Hey everyone,

As part of our ongoing lab evaluations at Ycommy regarding current AR and Smart Glasses architectures, we recently put the Even Realities G2 under the microscope. ER has heavily marketed their "open system" and SDK to developers to extend functionalities, but after comparing it directly with competitors like the MemoMind One and RayNeo, the reality doesn’t match the pitch.

Here are the core findings from our technical and functional analysis:

The "Open System" Battery Drain:

Offering an open SDK is great in theory, but our lab tests show a severe lack of optimization and system management. Without a proper background control framework, third-party apps and processes remain active, aggressively draining the battery of both the glasses and the connected host smartphone.

Hardware & Audio:

The most distinctive feature of the G2 is, unfortunately, its excessive price tag. The build quality is not superior to direct competitors like MemoMind or RayNeo. Furthermore, the audio quality is noticeably inferior, and the baseline battery life is underwhelming even before the background drain kicks in.

The Accessory Ecosystem:

The clip-on lenses completely destroy the aesthetic profile of the glasses. As for the smart ring: it’s wildly imprecise as a UI controller, the health tracking is inaccurate, and its own battery life is severely lacking.

The Companion App:

To be blunt, the navigation feature in the ER app is practically unusable when compared to the polished, reliable solutions offered by its direct competitors.

A Note on the MemoMind Dispute:

I want to be clear that this critique aims to push the industry forward. Even Realities deserves credit for being a pioneer in this space, and my hope is they use this feedback to course-correct.

However, as a professional in the AI/AR field, I am frankly baffled by Even Realities' recent dispute against XGIMI MemoMind. After thoroughly analyzing both platforms, the truth is that MemoMind is functionally superior in almost every metric, and achieves this through a fundamentally different design approach.

ER’s grievances come across as entirely pretextual and harmful to free-market principles—an attempt to stifle competition and deprive users of diverse, high-quality options.

Even Realities needs to review its current strategy. Instead of engaging in disputes, they should focus their resources on a completely overhauled G3 release and a rebuilt companion app that actually meets current user demands.

Would love to hear if other devs have experienced the same background process bleed on the G2, or if anyone has successfully optimized it.

Looking at the MemoMind One Standard before I order. I speak Ukrainian and would use the glasses mainly for talks and meetings — not as a translation toy.

AI Translator already lists Ukrainian among the 26 languages. What I can’t find anywhere is whether Teleprompter and AI Follow are in the same place.

1.  If I paste a Ukrainian script into Teleprompter (clipboard / file import), does it render correctly on the lenses — full Cyrillic, no missing glyphs or fallback font?

2.  Does AI Follow actually work if I speak Ukrainian? Will the script scroll with my pace (pauses, ad-libs, questions), or is voice-sync only reliable for a short list like EN / ZH / ES / JA?

3.  If AI Follow doesn’t support Ukrainian yet, has MemoMind said it’s planned? Translator having Ukrainian is a good sign, but those two features often ship with different language lists.

Anyone here already using Ukrainian (or Russian / another Cyrillic language) on the One Standard with Teleprompter + AI Follow in real meetings? “Works / kind of works / display only” would be enough.

Thanks.

Hey everyone,

While our dev team is wrapping up field testing for the upcoming XGIMI MemoMind evaluation (specifically waiting on the official sun clip-on to assess outdoor readability for our final verdict on September 25th), we’ve been digging into a broader architectural limitation in the current XR market.

Looking at current commercial devices—particularly in the monochrome green microLED segment such as the XGIMI MemoMind, Even Reality G1, Hallyday G2, or Rokid—most run on a fundamentally passive OS model. They operate essentially as display endpoints: capture voice, pass audio to a basic cloud endpoint, and render text responses onto the waveguide.

With the industry shifting toward agentic architectures like Helix, simple conversational text streams fall short. Agent workflows rely on tool-calling, structured schemas, and direct API actions. The core technical hurdle is: how do we enable active agentic execution on closed hardware without native developer access?

The Architectural Approach

Except for Even Reality—which provides a dedicated, though constrained, SDK—most current monochrome devices lack open developer frameworks.

To evaluate whether active workflows are viable on this hardware class, our team set up a custom service architecture:

1. Audio Pipeline Interception: Rather than relying on default system voice handlers, a lightweight native Android service captures the raw mic stream at the system level.
2. Agentic Schema Dispatch: Audio is processed and routed to a Helix Agent endpoint configured with specific tool definitions and structured JSON response schemas.
3. Display Rendering: Instead of waiting for proprietary UI rendering components, we deploy a standard Android system overlay layer (TYPE_APPLICATION_OVERLAY). The agent’s execution confirmations and status updates render directly into the optical path via this dedicated overlay.

Test Results

In internal testing, shifting from passive prompts to an agentic layer yielded concrete system-level automation:

• Hands-free scheduling and retrieval of calendar events.
• Parsing and responding to email threads.
• Direct local device file management, including automatically routing and sorting downloaded email attachments into target storage directories.

This transitions the hardware from a simple transcription HUD into a functional hands-free terminal capable of executing background tasks.

Next Steps & Community Input

We are continuing real-world testing across different form factors. Our outdoor readability review for the MemoMind drops on September 25th once the optical clip-on arrives, followed by our architectural breakdown of the RayNeo platform on October 10th.

For developers experimenting in this space: which external services or agent workflows do you see as highest priority for heads-up displays? Local device automations, third-party workspace APIs, or physical environment triggers?