Jualokal

The description states that Jualokal is a privacy-first marketplace for portable secondhand goods. It supports local handovers where:

• Sellers publish fixed-price listings.
• Buyers discover items through map or list views with coarse location data.
• The seller controls the handover process, including selecting an outdoor Handover Point and proposing time windows.
• A simulated checkout flow includes:
  • Five-minute Checkout Hold
  • Simulated Payment & Escrow
  • Presence Checks
  • Item Inspection against a frozen Purchase Snapshot
  • Confirmation steps to complete or refund the sale

The system is designed to avoid revealing sensitive data like home addresses, exact locations, or real-time movement. It also includes recovery paths for mismatches and refunds.

Inference The product is described as a mobile-first web application, built using React, TanStack Router, Supabase, and AI-assisted development tools.

The description states that Jualokal was inspired by the idea that selling locally often feels harder than selling far away. It positions itself as an alternative to traditional online marketplaces by focusing on:

• Local exchange
• Seller control over handovers
• Privacy protection for both parties
• Structured, accountable transactions

It claims to be a privacy-first marketplace, where the process is built around trust and accountability rather than just listing and shipping.

Inference The positioning evolved from a general problem (local secondhand sales being difficult) into a specific solution (structured, privacy-safe local handovers).

The description states that Jualokal targets:

• Buyers who want affordable secondhand goods but need confidence about the item and the person.
• Sellers who do not want to arrange delivery or invite strangers into their homes.

It also implies a local, urban Indonesian user base, given the context of traffic, distance, and coordination issues in Indonesian cities.

Inference The ICP is likely urban Indonesians with access to smartphones and interest in secondhand goods, particularly those who value privacy and local exchange.

The description does not state any pricing model or revenue mechanism. It only mentions:

• Fixed-price listings
• Simulated escrow and payment
• No real money processing
• No mention of fees or commissions

Inference The business model is not evidenced in the self-report.

The project was built using:

• Frontend: React, TanStack Router, TypeScript, Vite, Tailwind CSS
• Backend: Supabase, PostgreSQL
• AI tools: Codex, GPT-5.6
• Testing: Playwright
• Authentication: Supabase Auth

The team used a product brief and 19 decision records to maintain coherence during development.

Inference The technical stack is standard for modern web applications, with some AI-assisted development practices. The prototype is described as mobile-first, but no live or production deployment is mentioned.

The description states that:

• Jualokal is a hackathon prototype
• It includes a fictional Demo Mode for judges
• No real-world data, customers, or adoption are reported
• The demo contains fictional buyers, sellers, listings, and transactions but does not process real money or identity

Inference There is no evidence of traction, revenue, or customer adoption beyond the prototype.

The description does not mention any competitors. It only positions Jualokal as a different approach to secondhand commerce — one that emphasizes local exchange and privacy over shipping and platform-scale listings.

Inference No competitive analysis is provided in the self-report.

• Prototype-only: The product is not a live or production-ready system.
• No real-world data: No evidence of customers, revenue, or usage.
• Simulated outcomes: All transactions are fictional or simulated — no actual escrow, payment, or identity verification.
• Unverified claims: The description makes strong claims about privacy and trust but does not provide evidence of implementation or testing.

Inference The project is a conceptual prototype, not a commercial product. Risks include lack of real-world validation and potential misalignment between the idea and execution.

1. What are the key assumptions about user behavior that underpin this design?
2. How does the team plan to transition from demo mode to live, real-world transactions?
3. Are there any plans for integrating real identity verification or payment systems?
4. What is the expected timeline for moving beyond prototype status?
5. Has the team tested the product with actual users in Indonesia?