A sharper front door, harder edges, and native ownership underneath.
The landing page, company page, security posture, mobile shell, and shared-code architecture all moved toward a cleaner and more durable product.
The front door finally looks like the product we are building
The marketing experience got a premium reset: calmer typography, cleaner storytelling, stronger product positioning, and fewer generic SaaS gestures politely waving at no one.
The new company surface also gives Lernex a clearer trust footprint with verified business information, legal routes, support routes, and SEO metadata that match the product's real identity.
Landing page polish
The public site now leads with the continuous learning relationship instead of a pile of disconnected features.
Company verification
A dedicated company page makes trust, contact, and public identity easier to verify.
Support alignment
Support knowledge and public surfaces were kept aligned so the app does not explain yesterday's version of itself.
Shared-core limbo started getting dismantled
A lot of behavior that had been living in shared core moved into platform-owned homes. Web behavior went to web. Mobile behavior went to mobile. Native reader behavior started getting real Swift and Kotlin surfaces.
That matters because cross-platform does not mean every platform should wear the same oversized coat. It means the product contract stays aligned while each platform uses the right tools.
- Native lesson reader shell for iOS and Android.
- Platform-owned navigation, companion contracts, Learning DNA, rewards, subscriptions, uploads, and visual parsing.
- Separate iOS and Android navigation implementations with aligned learner-facing behavior.
- Migration cleanup in shared core so old helper files do not become permanent archaeology.
Security hardening moved from audit to code
The release included concrete hardening across shared document cache policies, auth-adjacent flows, usage logging, public profile access, and dependency surfaces.
This is the unromantic part of building a learning product: if students trust the app with class material, notes, progress, and mistakes, the system has to treat those records like they matter. Because they do.
The GitHub security-hardening audit was merged during this release window.
Shared document cache and usage-log access paths were tightened.
Company, privacy, terms, and support surfaces became more coherent.
The future thread system started here
v1.6 also laid the backend rails for the durability work that becomes visible in v1.7: study-thread tables, chat feedback rollups, SAT continuity events, Generate-FYP bridge lifecycle tracking, and better model pricing coverage.
It is infrastructure, which means when it works nobody notices. That is the compliment and the curse.
The product got more credible above the waterline and sturdier below it.
v1.6 was about making Lernex feel premium in public while making the underlying architecture less fragile, less shared-core-dependent, and more ready for native depth.