Archive position — measured, not model output
0 likes on Devpost
2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #5,726 place in the like-ranked listing is a tie-break inside that group, not a ranking.
Projects (log scale)
Likes on Devpost. ▲ marks this project's group.
Show the figures
| Likes | Projects | Share of archive |
|---|---|---|
| 0 | 5,592 | 71.2% |
| 1 | 1,758 | 22.4% |
| 2 | 285 | 3.6% |
| 3–4 | 132 | 1.7% |
| 5–9 | 75 | 1.0% |
| 10+ | 14 | 0.2% |
Executive Summary
What the company appears to be
OPION is a mobile-first news PWA that presents real-world events through multi-source reporting, allowing readers to compare perspectives, trace evidence, and form their own judgments. It builds on a backend system called Perspectra, which clusters news articles into events and tracks provenance.
What changed
The author states that OPION emerged from an earlier project, Perspectra, which was a backend for grouping reports about real-world events while preserving source links. During Build Week, the author transformed this backend idea into a product with a mobile PWA interface and an "Ask Opion" investigative tool.
Single most important open question
Is there any evidence of actual user engagement or adoption beyond the curated MVP? The description does not indicate whether OPION has moved past its demo state or if it has begun collecting real data or users.
What The Product Actually Is
The description states that OPION is a mobile-first news PWA with two main sections:
- My Feed, which displays one event at a time in an immersive layout,
- Ask Opion, which provides structured analysis of the event using multi-source evidence.
It uses a backend system called Perspectra, which clusters articles into events and tracks their provenance. The product includes features such as:
- Topic filters
- Saved stories
- Sharing
- Comments
- Read Aloud controls
- Offline states
- Accessibility support
The MVP curates 18 real multi-source events from Perspectra, removing flagged articles and preserving original links.
Evidence
- The author describes OPION as a PWA built with Next.js, React, TypeScript.
- It includes a feed layout and an "Ask Opion" interface.
- It uses Groq for server-side processing of event data.
- The system is designed to show where claims come from via citations.
Inference The product is described as a solo-built MVP, not yet a production-grade service.
Positioning & Claim Evolution
The author states that OPION was built to address the problem of biased news reporting, where readers only see part of a story depending on which publisher they read. It is not intended to label publishers or tell readers what to believe, but instead to show different perspectives side-by-side and let users judge for themselves.
The positioning is:
- A tool for multi-perspective journalism
- Focused on evidence tracing
- Designed to preserve uncertainty, not resolve it
It builds on a prior research project (Perspectra) and a university thesis, suggesting a research-driven approach rather than a commercial one.
Evidence
- The tagline: “See every side of the story, trace the evidence, and judge for yourself.”
- The author explicitly says it is not about labeling bias or dictating belief.
- It uses a backend system (Perspectra) that was previously documented in academic work.
Inference The positioning implies a trust-building tool, not a news aggregator or opinion platform.
Target Customer & ICP
The description does not clearly define a specific customer segment or ideal customer profile (ICP). It is implied that the target audience includes readers who want to understand complex events from multiple angles and value transparency in sourcing.
It is described as a news PWA, suggesting it targets users of mobile news platforms, but no explicit demographic or behavioral targeting is stated.
Evidence
- The product is built for readers seeking multi-source event coverage.
- It supports mobile-first experience, implying a mobile audience.
- It includes features like offline support and accessibility, which may appeal to a broad user base.
Inference The ICP likely includes informed readers, researchers, or news-savvy users who want to go beyond surface-level reporting.
Business Model & Pricing Evidence
There is no evidence of any business model or pricing structure in the description. The author states that OPION is a solo-built MVP and not yet a production-grade service.
Evidence
- No mention of monetization, subscriptions, ads, or paid features.
- The MVP is described as a curated snapshot, not a live news pipeline.
Inference The business model is not yet defined, and the product appears to be in an early-stage demo phase.
Technical & Delivery Signals
The author states that OPION was built using:
- Next.js, React, TypeScript
- Zustand for state management
- Playwright for testing
- Groq for server-side processing of event data
- Codex and GPT-5.6 for development assistance
It is a PWA, with support for:
- Offline behavior
- Installation
- Accessibility features (e.g., large text, reduced motion)
- Mobile-safe layouts and keyboard handling
The backend system (Perspectra) includes:
- Semantic clustering
- Multi-signal event matching
- Human review for uncertain matches
- Event database with articles and provenance
Evidence
- The author describes the tech stack used in building OPION.
- It uses Groq to structure answers, but only validates against curated source IDs.
Inference The technical architecture suggests a modular, scalable design, though it is currently limited to a curated MVP.
Traction & Maturity Signals
There is no evidence of traction or adoption beyond the MVP. The author states:
- The demo includes 18 curated events.
- It is a stable snapshot, not a live news pipeline.
- No revenue, customers, or user engagement data are provided.
Evidence
- The MVP is described as a curated set of real events, not a live system.
- No metrics on usage, retention, or user feedback are mentioned.
Inference The product is in an early-stage demo phase, with no signs of real-world traction.
Competitive Context
The description does not mention any direct competitors. It is implied that OPION fills a gap in how news is consumed by offering:
- Multi-source event coverage
- Transparent sourcing
- Structured investigation tools
It is positioned as a news PWA with an investigative layer, which may differentiate it from traditional news aggregators or opinion platforms.
Evidence
- No mention of competitors.
- The product is described as a multi-perspective journalism tool, not a general news reader.
Inference The competitive landscape is unclear, but OPION appears to be in a niche space focused on transparency and evidence-based reporting.
Key Risks & Red Flags
- No traction or user data: The product is described as an MVP with no real-world usage.
- Limited backend capacity: The author notes that source recall was limited due to external search provider constraints, which may affect scalability.
- Solo builder: The entire project was built by one person (Wasik Yousha), raising questions about long-term maintainability or growth.
- Unclear monetization path: No business model is described, making it hard to assess viability.
- MVP scope: The demo is limited to 18 events and does not reflect a live news pipeline.
Evidence
- The MVP is described as a curated snapshot, not a live system.
- The author notes limitations in backend scalability.
Inference The product is at risk of remaining a demo-only tool, with no clear path to production or monetization.
Diligence Questions To Ask The Founders
- What is the plan for scaling beyond the 18 curated events?
- How will the system handle real-time news ingestion and updates?
- Is there any intention to monetize the product, and if so, how?
- What are the limitations of Groq integration in terms of accuracy or reliability?
- Are there plans to expand beyond news into other domains like research papers or government filings?
- How is user feedback being collected or tested in the MVP phase?
- What are the long-term goals for the Perspectra backend system?
Investment/Partnership Verdict
Not evidenced.
The description does not provide any evidence of revenue, customers, traction, or a clear path to monetization. It is a solo-built MVP with no indication of real-world adoption or commercial viability.
Confidence Low This is a self-reported, unverified account of a demo product. The author states that the project is not yet a production-grade service and has not moved beyond its curated MVP phase.
Inference There is no basis to assess whether OPION is ready for investment or partnership at this stage. It appears to be an early-stage concept with potential, but lacks any commercial signals.
Source
Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.
The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.