Flowiki

The description states that Flowiki is a hybrid-canvas note app for Android tablets (package com.feng.suixinji). It places the following onto a single page coordinate system:

• Stylus writing: captures $x, y, t, p, \tau, \phi$ and tool type; pressure pen, highlighter, eraser, lasso, shapes
• Hybrid canvas elements: ink, text, tables, images, stickers, formulas, charts (PlotElement), masking tape, attachments, audio
• AI Studio: streaming Markdown, KaTeX-style formulas ($...$ inline, $$...$$ block), flowcharts, whiteboard tool calls
• BYOK model interface: users bring their own Chat / Image / Embedding endpoints; credentials are protected by Android Keystore, no developer keys shipped
• Local WebView search: queries go to the user's chosen search engine and the app fetches result pages directly
• Scientific chart gallery: 10 categories, 69 templates — from basic line plots to noisy Gaussian peak LM fitting, Savitzky-Golay smoothing, arPLS baseline correction
• Chart digitization (Datapicker): pick an image element on the canvas → calibrate two axis reference points → tap-to-sample → generate a data column and build a chart

Everything is offline-first: canvas rendering, numerical algorithms, formula typesetting all run on-device. AI is a pluggable capability, not a prerequisite.

The description states that Flowiki was built to address a tension between "paper-like feel" of tablet handwriting and "compute power" of AI tools. It positions itself as an alternative to existing note apps that either perfect the paper-like experience (GoodNotes, Noteshelf) or AI capabilities (NotebookLM, ChatGPT), but not both.

The authors claim it allows students to take notes by hand and have AI continuation appear in their own handwriting style, researchers to drag PDFs onto canvas and get answers with clickable citations, and engineers to pull up scientific charts mid-lecture and perform fitting.

This is a self-reported positioning statement — no evidence of market validation or customer feedback is provided.

The description does not state specific target customers or ideal customer profiles (ICP). It mentions use cases involving students, researchers, and engineers, but does not define who the primary users are or how they would be segmented.

Not evidenced.

The description does not contain any information about business model or pricing. There is no mention of monetization strategy, subscription tiers, freemium structure, or sales channels.

Not evidenced.

The project was built using:

• Language: Kotlin
• UI: Jetpack Compose + Compose Material 3 1.5.0-alpha23
• Handwriting: AndroidX Ink + custom PressurePenEngine
• Recognition: ML Kit Digital Ink Recognition
• Networking: OkHttp + SSE decoder
• Build: Gradle Kotlin DSL + Version Catalog, minSdk 28 / targetSdk 36 / compileSdk 37

Key architectural decisions include:

1. Four-layer ink data — semantically aligned with InkML but stored as a versioned binary structure rather than XML
2. Unified canvas element model — CanvasElement is a sealed interface
3. PlotElement renders through one pipeline in three places — canvas element, editor preview, and gallery card all consume the same PlotRenderSpec
4. All numerical algorithms are hand-written in pure Kotlin — this is the project's lifeline
5. FormulaEngine.kt — a native LaTeX typesetting engine written to replace KaTeX WebView
6. Material 3 Expressive design system — theme name Ink & Paper

The app is described as offline-first with no cloud dependency for core compute.

There is no evidence of traction or maturity beyond the hackathon submission. The description states that this project was submitted to the OpenAI 2026 hackathon on Devpost and that no revenue, customer or traction data is available beyond what they state.

Not evidenced.

The description mentions GoodNotes, Noteshelf, NotebookLM, and ChatGPT as existing note apps in two camps — one perfecting paper-like feel, the other AI capabilities. It also references LabPlot's scientific plotting capability matrix and W3C InkML's digital ink semantics.

However, no competitive analysis or market positioning relative to these tools is provided beyond the claim that Flowiki aims to bridge their gap.

Not evidenced.

1. No commercial traction or revenue: The project is described as a hackathon submission with no evidence of monetization or user adoption.
2. Experimental tech stack: Uses alpha versions of Material 3 Expressive APIs and experimental features.
3. High engineering complexity: Hand-wrote complex numerical algorithms in Kotlin, which may not scale well without dedicated teams.
4. Limited platform scope: Only Android tablets are mentioned; no cross-platform support or mobile web is discussed.
5. Self-reported maturity: All claims are self-reported and unverified.

1. What is the current status of Flowiki beyond the hackathon submission? Is there any user testing, beta program, or early adopter feedback?
2. How do you plan to monetize this product? Are there any revenue models or pricing strategies in development?
3. What are the technical challenges you anticipate scaling this app to a larger user base?
4. Have you considered how to integrate with existing productivity ecosystems (e.g., Google Workspace, Microsoft 365)?
5. How do you plan to handle data privacy and security, especially given the BYOK model interface?