Nadi

The description states that Nadi is a native Android app built with Kotlin and Jetpack Compose. It processes optional Android signals such as screen sessions, app transitions, movement, phone orientation, media, volume, brightness, ambient light, calls, location areas, steps, headphone context, and notification rhythm.

It collects raw events via collectors and Android services, reduces them into small local summaries stored in SQLite, and uses pattern engines to compare compatible days only after sufficient coverage exists. The interface presents results as a readable daily flow with evidence sheets.

The product is described as intentionally conservative: each insight can reveal its supporting evidence, coverage, comparison, and limitations. Missing evidence stays missing rather than becoming zero.

Inference Nadi is an on-device analytics tool focused on personal usage patterns, not enterprise or public data analysis.

The author positions Nadi as a calmer alternative to existing digital wellbeing tools, which typically stop at hours and app charts. Nadi aims to explain the rhythm behind screen time—when someone kept returning, what clustered together, or how today differed from their own baseline.

It emphasizes:

• Local processing of data
• Transparency in what is known vs. unknown
• Privacy by reduction (not retaining raw coordinates, notification content, or app identities)
• Explainable insights with evidence and limitations

The description also notes that Nadi avoids turning signals into psychological diagnoses or unsafe behavioral inferences.

Inference Nadi positions itself as a privacy-conscious, transparent, and user-centric tool for personal screen-time analytics.

The description does not explicitly identify a target customer or ideal customer profile (ICP). It implies that Nadi is intended for individuals interested in understanding their own screen usage patterns, particularly those who value privacy and want deeper insight than standard charts offer.

It suggests a focus on users who are concerned about digital wellbeing but do not want to share intimate behavioral data with cloud services.

Inference The ICP likely includes privacy-conscious individuals or early adopters of personal analytics tools. No specific demographic or persona is defined.

There is no evidence in the description regarding a business model or pricing structure for Nadi. The project appears to be a hackathon submission, and there is no indication that it has moved into monetization or sales channels.

Inference If Nadi is intended for commercial use, its business model remains unknown. It may be a freemium app or a standalone tool without a clear monetization path at this stage.

Nadi is built using Kotlin and Jetpack Compose, with collectors and Android services reducing raw events into local summaries stored in SQLite. The architecture includes pattern engines that compare compatible days only after enough coverage exists, and the interface presents results as a readable daily flow with evidence sheets.

Codex with GPT-5.6 was reportedly used to assist in mapping platform constraints, implementing pipelines, designing UI, challenging unsafe inferences, handling partial coverage, and running verification loops across tests, lint, builds, and real-device QA.

The repository preserves the resulting architecture, tests, decisions, and setup guidance.

Inference The technical stack supports an on-device, privacy-first approach. The use of AI assistance suggests a modern development methodology.

There is no evidence of traction or user adoption beyond the hackathon submission. The project is described as a working Android product rather than a sensor proof of concept, and includes extensive automated tests and real-device verification.

However, there are no mentions of:

• Users or downloads
• Feedback from users
• Market testing or pilot programs
• Any form of commercial traction

Inference Nadi is at the prototype or early-stage development stage. No evidence of user engagement or market validation.

The description does not provide information about competitors or how Nadi fits into the broader digital wellbeing or personal analytics space. It only contrasts Nadi with "most digital wellbeing tools" that stop at hours and app charts, suggesting a niche in privacy-conscious personal analytics.

Inference Nadi likely competes within the broader personal analytics or screen-time management space. It may be positioned against apps like Moment, Forest, or similar tools that offer basic tracking but lack Nadi’s emphasis on privacy and explainability.

• No commercial traction or user feedback: The project is only described as a hackathon submission with no evidence of real-world usage.
• Unclear monetization strategy: No indication of how Nadi would generate revenue or scale beyond the prototype phase.
• Limited scope for growth: The focus on local processing and privacy may limit its appeal to users seeking cloud-based insights or integration with other platforms.
• Unverified claims: All descriptions are self-reported and unverified; no third-party validation exists.

Inference The lack of traction raises questions about viability as a commercial product. The privacy-first approach may also limit scalability or appeal in certain markets.

1. What is the current status of Nadi beyond the hackathon submission? Is it being used by anyone outside of the development team?
2. How does Nadi plan to scale its user base or monetize the product if it moves beyond prototype?
3. Has there been any feedback from users on the value of explainable insights versus simple charts?
4. What are the technical challenges in expanding support across different Android vendors and versions?
5. Are there plans to integrate with other platforms or services, or is the focus purely on local processing?