NexID: from TAP to product, with a clearer experience

A reading people can understand

A connected product needs more than an attractive screen. People want to know what they are looking at, what result they received when bringing their phone close, and what they can do next. In October, NexID reorganized SUN to show the product and the complete reading result first, with supporting details available progressively.

The Ni identity incorporates a finite animation and gives photographs more space. The design supports light and dark themes, reduced motion and forced colors. Relevant warnings remain visible. This combination tells the product's story more clearly while keeping the reading status visible through the visual effects. The SUN update documents the change and its checks.

Location through an explicit decision

Location appears as a visible option when appropriate for a fresh reading. People decide whether to share it. After server confirmation, the interface shows city and country when available, explains the approximate source of the information and offers an action to open the map.

The benefit is practical: customers can understand the information they contributed, and brands can design a contextual experience with optional geolocation. The product preserves an important distinction between an approximate reference and a location obtained with permission; that precision is also part of a good interface.

Continuity when something fails

The improvements reach the customer portal and its destinations. If a session lookup is temporarily unavailable, the screen offers recovery and preserves the route and its parameters. A genuine access denial retains the appropriate login journey. A temporary problem therefore becomes more understandable, and users keep the product's context.

Brands and marketplace also distinguish an empty catalog from a source that did not respond. When information is missing, unknown points or counts appear as unavailable and the interface offers a retry. This avoids communicating false zeros or suggesting that records disappeared. The customer continuity update explains that behavior.

Brands control what they publish

The dashboard editor now connects to the persisted catalog that customers consult. The workflow separates saving a draft, making the brand visible, publishing a product and withdrawing it. Each operation requires current authorization for the selected organization and revision checks that prevent one concurrent change from overwriting another.

Forms preserve work through validation, permission and network errors. If a save response is lost, the state is read back before another deliberate attempt. This continuity makes the catalog manageable and reduces the distance between what a brand prepares and what its customer sees. The changes are documented in the editorial dashboard and its publication API.

What is published and what remains open

As of October 6, the web, API and dashboard versions containing these improvements were connected to their production domains and ready on Vercel. Interface, contract and isolated persistence checks exist; the complete journey from physical TAP to persisted location and an authenticated CRM lookup still needs its own acceptance.

Publishing a product also does not confirm payment, stock, rewards or physical ownership. Those outcomes require their own evidence. You can explore NexID and its connected product offering with that clear distinction between published functionality and operations that have actually been verified.