Fleetic Keyboard

The description states that Fleetic is a native Android keyboard built using AOSP LatinIME as its foundation. It integrates GPT-5.6 to refine workplace messages in real time, but only after the user explicitly taps "Refine". Key features include:

• Communication DNA: A structured profile derived from a writing sample and refinement priority.
• Refinement is intentional: text is not sent until the user confirms.
• Text ownership is conservative: the keyboard replaces only what it can prove it owns.
• The system fails safely if replacement cannot be verified.

The product is described as an input method that works within existing Android apps (e.g., Slack, email clients), and does not replace the entire messaging experience.

Claim

Fleetic is a native Android keyboard with AI-assisted refinement.

Evidence Author's own description.

The author positions Fleetic as an alternative to generic grammar checkers or chatbot keyboards, emphasizing:

• User voice preservation: The output should sound like the user.
• Intentional sending: No automatic replacement; users must tap Refine.
• Privacy-first design: No message content is stored or logged.
• Trust boundary: Text replacement only happens when ownership can be verified.

The positioning evolves from a technical solution to a trust-based communication tool, where the AI’s role is to assist without altering identity.

Claim

Fleetic aims to reduce hesitation before sending messages by refining them naturally, while preserving user voice.

Evidence Author's own description.

The author describes the target audience as:

• Professionals working in English who are not native speakers.
• Users who experience hesitation or context-switching when typing short workplace messages (e.g., Slack, email).
• Individuals who want AI help but do not want to lose their communication identity.

There is no explicit segmentation beyond this general user group. No named customer types, personas, or use cases are provided.

Claim

Fleetic targets professionals working in English as a second language.

Evidence Author's own description.

The description does not contain any information about:

• Revenue streams
• Pricing models
• Monetization strategy
• Customer acquisition costs
• Sales process or go-to-market plan

It is unclear whether the product is intended to be free, paid, or offered via subscription.

Claim

No business model or pricing evidence provided.

Evidence Not evidenced.

The author provides detailed technical information:

• Built on AOSP LatinIME
• Uses Kotlin, Java, C++, Jetpack Compose, and Android Views
• Backend in Go with Chi, PostgreSQL (via pgx), Distroless containers
• Communication DNA is structured into six dimensions: brevity, formality, warmth, directness, vocabulary, expressiveness
• GPT-5.6 is used via OpenAI’s Responses API
• Uses strict schema validation and idempotent request handling
• Includes tests covering contracts, handlers, prompt invariants, and Android API client behavior

The product was tested on a physical Samsung Galaxy A54 running Android 16.

Claim

Fleetic is built with strong technical rigor, including privacy-conscious design and safety mechanisms.

Evidence Author's own description.

There is no evidence of:

• User adoption or retention
• Revenue or monetization
• Customer feedback or usage metrics
• Product roadmap or iteration history beyond the MVP
• Any form of market validation

The project is described as a Build Week hackathon submission, and no mention of launch, beta testing, or user engagement.

Claim

No traction or maturity signals.

Evidence Not evidenced.

The author does not reference any competitors directly. However, the product’s positioning implies it competes with:

• Generic AI keyboards
• Grammar-checking tools (e.g., Grammarly)
• Chatbots integrated into messaging apps

It distinguishes itself by focusing on user identity preservation, intentional refinement, and trust boundaries.

Claim

Competes in the AI-assisted writing space, with a focus on trust and identity.

Evidence Author's own description.

Several risks are implied by the description:

• No commercial traction or monetization: The product is not yet launched or monetized.
• Limited scope: Only supports Android; no iOS or desktop plans mentioned.
• High technical complexity: Integrating AI into a keyboard with trust and safety constraints may be difficult to scale.
• Unproven user need: No evidence of market demand or user feedback beyond the developer’s own experience.
• Dependency on GPT-5.6: The system relies heavily on a proprietary model, which could introduce risks if access changes.

Claim

Risks include lack of traction, limited scope, and unvalidated assumptions.

Inference Based on absence of evidence for commercial viability or user feedback.

1. What is the expected timeline to market?
2. How will you validate that users actually want this product?
3. Are there any plans to expand beyond Android?
4. What are your assumptions about user behavior and adoption?
5. How do you plan to handle model drift or degradation over time?
6. Is there a plan for user onboarding or education around Communication DNA?
7. What are the key metrics you would track post-launch?

Claim

These questions are necessary due to lack of evidence around traction, user validation, and commercial strategy.

Inference Based on absence of data.