Mohalla AI

The description states that Mohalla AI is a location-based community platform for reporting and discovering neighborhood updates. It includes:

• A GPS-aware mobile feed, where residents can post safety alerts, report problems (e.g., water shortages), request help, and share local events.
• Anonymous posting capabilities to protect identity.
• An optional AI Post Assistant, which:
  • Turns informal messages into clearer community posts
  • Suggests categories
  • Optionally translates into English or Hindi
• The assistant is implemented via a Supabase Edge Function connected to OpenAI API, with structured outputs and caching.

Not evidenced There is no evidence of actual product usage, customer base, or monetization. The AI assistant is described as disabled in the public test build due to billing constraints.

The author states that Mohalla AI was created to address a problem: important neighborhood information is scattered across noisy messaging groups and social media, often getting buried or reaching irrelevant audiences.

It positions itself as:

• A privacy-conscious platform for local community communication.
• A tool that makes community updates more useful and local.
• An AI-assisted experience that enhances but does not control user input.

The product is described as a "digital neighbourhood layer", aiming to allow residents to quickly share information and collaborate on solving local problems.

Inference The positioning implies an intent to build a scalable, community-driven platform. However, no evidence of traction or adoption exists.

The description states that Mohalla AI is intended for:

• Nearby residents, who can publish safety alerts, report problems, request help, and share local events.
• Users in India, given the inclusion of Hindi translation and local context.

It also mentions support for RWAs (Residential Welfare Associations), local volunteers, and municipal authorities as part of its long-term goals.

Not evidenced No evidence of actual users or customer segments beyond the description. No mention of specific demographics, usage patterns, or target markets.

The description does not state a business model or pricing strategy.

It mentions that:

• The AI assistant is optional
• Residents remain in control of publishing decisions
• The platform supports anonymous posting and local identity management

Not evidenced No evidence of monetization, subscription plans, or revenue streams. No pricing information is provided.

The project was built using:

• Flutter (mobile app)
• Dart
• Riverpod (state management)
• GoRouter (navigation)
• Supabase (authentication, storage, Edge Functions)
• Firebase Cloud Messaging (notifications)
• OpenAI API (via Supabase Edge Function)
• PostgreSQL (storage and row-level security)

The AI assistant is implemented via:

• Structured outputs
• SHA-256-based caching
• Usage limits (3 generations per user/day)
• Server-side secret management

Not evidenced No evidence of production deployment, scalability, or infrastructure beyond the prototype.

The description states that this is a hackathon project submitted to OpenAI 2026, built during OpenAI Build Week.

It includes:

• A public test build (with AI disabled due to billing)
• A complete authenticated integration, structured-output contract, caching system, and usage controls in the repository
• Plans for future features like geospatial filtering, multilingual support, and moderation

Not evidenced There is no evidence of user adoption, customer feedback, or product maturity beyond prototype status.

The description does not mention any competitors. It does not state whether similar platforms exist in the market or how Mohalla AI differentiates from them.

Not evidenced No competitive analysis or positioning against existing tools for community communication or local issue reporting.

• Prototype-only status: The project is described as a hackathon submission, with no evidence of production use.
• AI assistant disabled in public build: Suggests incomplete development or cost constraints.
• No monetization strategy: No indication of how the platform would generate revenue.
• No customer or user data: No evidence of traction, adoption, or feedback.
• Single founder team: The project is built by one person (Zakir Husain), which may limit scalability.

1. What is the current status of the product? Is it in production or still a prototype?
2. Have you conducted any user testing or gathered feedback from residents?
3. How do you plan to scale beyond the hackathon version?
4. Are there any plans for monetization or revenue generation?
5. What are your long-term goals for community engagement and platform growth?
6. How do you intend to manage misinformation or abuse in the local feed?