Lets Product Paper

Product status: preparing for a closed beta

Information reviewed: July 15, 2026

This document explains in plain language what Lets is today. It separates features already supported by current evidence from areas that are still under review. It is not a promise of future features or an announcement of a public launch.

1. What Lets is

Lets is a mobile social app with a feed, stories, profiles, search, messages, and Circles.

In Lets, people can follow posts, share their own, talk, and gather around a shared activity or topic. No specialist terms are needed to get started: the app is built on a familiar social foundation.

At this stage, Circles are the main distinguishing part of Lets. They keep shared context from getting lost: members, posts, chat, useful materials, and questions stay in one place.

2. A familiar social foundation

The social side of Lets uses familiar formats:

• Posts let people share material, receive reactions, and discuss it.
• Stories provide a short format for current events and moments.
• Profiles show a person and their posts.
• Search helps people find other people and topics of interest.
• Messages let people continue a conversation directly.

These features already exist in the current app. However, the presence of a feature does not mean that every path through it has completed final checks on all devices and under all network conditions. That is why the current product status is preparing for a closed beta.

3. Circles

A Circle is a place for people who share a common context. It is more than a chat and more than a list of members.

One Circle can contain:

• members and clear roles;
• posts and a shared chat;
• useful materials;
• invitations and requests to join;
• questions for members.

The owner creates the Circle, invites people, reviews requests, and manages members. A person can see their status or role and the next action available to them: join, answer a question, open the chat, view materials, or return to posts.

This keeps related information close together. People do not have to search in different parts of the app for the continuation of the same conversation.

4. Questions in Circles

A Circle owner can write a question and provide several answer options. A member selects one option. One account keeps one choice; repeating the action does not create a second answer.

After the question is closed, the result remains visible. Members can return and see the recorded result.

Questions are currently created manually. A regular discussion does not turn into one automatically. A result records the members' view, but it does not change rules, start an action, or become a commitment from the Lets team by itself. If a next step follows a question, it must be communicated separately.

5. Personal space

Lets gives people specific controls rather than a broad promise of absolute privacy. In the app, a person can:

• choose who can see their profile and stories;
• decide who can send them messages;
• maintain a close friends list for stories;
• block people and manage the blocked list;
• review active sessions and end sessions they no longer need.

The app also includes a path to request account deletion. We do not promise that every related record disappears immediately: the final flow and rules for retaining required data are still under review.

These settings help people manage their space. They do not mean that the service stops processing data needed to operate the app.

6. Glints: limited social context

The product boundary for Glints is simple: they should be a small social signal next to the object or action they help explain. Glints may show context about attention and activity inside Lets, but they should not determine a person's status, affect how answers are counted, or become a separate primary product area.

Quality assurance (QA) status: risk remains open. Limited Android checks confirmed that the available Glints screen and the paths that open it use neutral social language. However, live activity data and an authenticated flow on the service intended for the closed beta, behavior on a physical device, and a complete manual TalkBack and VoiceOver pass have not yet been confirmed.

The current interface also retains a separate Glints summary screen. This does not fully match the intended form, where a Glint stays next to clear social context. For that reason, we do not describe the current form as final or present Glints as a main benefit of Lets until these checks are complete.

7. The boundary of closed beta preparation

The current status of Lets is preparing for a closed beta. This means the team is checking core flows in sequence, fixing unstable states, and gathering evidence for release builds. Checks for a public launch have not yet been completed across the whole app.

The current scope does not include tools for advertisers, advertising campaigns, paid reach, or financial features. Earlier internal work is not part of the beta and must not be shown to people as a current feature.

Message protection is still being reviewed and improved. The project does not make a blanket promise of the same protection for every kind of message.

Results from questions in Circles are also not a promise of implementation by the team. The Product Paper describes only what current evidence supports or what is clearly marked as still under review.

8. What has been checked and what is still under review

Checked

• The social foundation - posts, stories, profiles, search, and messages - exists in the current app.
• Core Circle roles and transitions were checked in a signed Android build on a physical Pixel with a local server. The check covered the owner, an invited person, joining, a join request, restoration after restart, large text, and reduced motion.
• Creating a question with options, keeping one choice per account, duplicate protection, closing the question, and retaining the result were checked in an authenticated release flow with a local server and automated tests.
• Visibility, messaging, close friends, blocking, and active-session controls are present in the current app.

Still under review

• authenticated use of all core flows on the service intended for the closed beta;
• a signed build on a physical iPhone;
• the complete spoken screen order reviewed by a person using TalkBack and VoiceOver;
• Glints with live data, their final placement next to clear social context, and accessibility;
• the final account-deletion flow and data-retention rules;
• any stronger public wording about message protection;
• a release decision for the whole app rather than separate verified slices.

How to read project news

Lets news should be read as dated reports about verifiable changes, not as promises. Each update should separate three things: what changed, what it gives people, and what has not yet been confirmed. If new evidence changes the status of a feature, the Product Paper and the public product description should be updated together.