Back to Journal

SmileChat enters PRELAUNCH: what is confirmed and what is not

A precise reading of product status, pending validation, and the meaning of public previews.

Reading sizeSaved only in this browser.

PRELAUNCH is a status, not a date

PRELAUNCH means SmileChat exists as a product under development and validation, but is not yet a publicly available service. The website provides no registration, download, invitation, or early access. There is also no confirmed public date. This avoids two misleading impressions: that everything is merely an idea, or that an interactive preview is the same as a launched application.

The status organizes the work and its communication. There are implemented features, an iPhone experience under testing, planned elements, and a broader product vision. Each group requires different evidence. A planned feature need not be under construction, and a vision idea can guide design without belonging to a calendar.

What the current source confirms

The status source confirms private 1:1 chats with end-to-end encryption; reply, edit, pin, and highlight; offline queueing, reconnection, and local search; Secret Chat v2; local identity; encrypted-backup recovery; and contact, invite, and identity-checking flows. “Confirmed” describes implementation according to current documentation. It does not mean someone can install the product today.

The distinction matters particularly for security. An implemented control may still require interface review, physical-device behavior checks, documentation, failure handling, and regression testing. The status page adds a current-reality note to each item so its label cannot be read without context. If the source changes, the site should change from that single point, not through scattered phrases.

What remains under testing

The iPhone experience requires further validation on physical devices before any public availability. The Web Beta is also reviewed continuously for bilingual content, navigation, contrast, keyboard use, reduced motion, and mobile layouts. Being online alone does not prove that every interaction or piece of copy is correct.

Automated checks exercise actions and routes, while visual review helps find language, layout, and motion problems. No individual tool certifies total quality, security, or legal accessibility. Moving forward requires several reliable signals together.

Planned does not mean promised

Android, groups, calls, and production notifications are planned. They have no public date or committed final scope. Full customization is also planned: previews show themes, shapes, particles, and atmospheres, but the set reaching a future product may change. Describing these elements as available would confuse direction with delivery.

We use “vision” for SmileChat Atmospheres as a broad system and for ideas such as music, mini-games, artificial intelligence, voice translation, and video covers. Vision enables exploration without turning every experiment into public debt. If an idea advances, it must move to a state backed by verifiable work. If not, the website should not preserve it by inertia as a promise.

What the previews actually do

Living Phone simulates a localized conversation. Visitors can write messages, reply by gesture or button, react to each message, use expressions, and change the atmosphere. Its scrolling belongs inside the chat and must not move the page during interaction. Initial names and messages are fictional and exist only to show interface behaviour.

My ideal chat lets visitors design atmospheres, profiles, and preferences across Phone, Tablet, and Desktop. It includes Playground, shareable settings, and local backgrounds. Everything happens in the browser and does not imply message delivery, account creation, or synchronization.

What would need to happen next

Leaving PRELAUNCH requires more than completing a visual checklist. The product must be validated on physical devices, critical flows closed, security reviewed, production notifications prepared, privacy and recovery documented, applicable terms defined, and a proportionate support process built. Planned platforms require their own work; they do not inherit a date merely by appearing on a page.

Until then, the most reliable way to follow the project is the status page and this Journal. The newsletter lets people leave a consented request and withdraw it from the same website. We also do not publish invented user metrics. When status changes, the update should explain what changed and what remains pending.

SmileChat newsletter

Follow SmileChat's development

Leave your email to request SmileChat updates when delivery becomes active.

You are in controlYou can withdraw your request at any time from this same block. The controller’s legal identity is pending confirmation.

Withdraw a request