STARTED WITH
the idea of making study a place for community
Neqraw
A social product around study and knowledge, built across mobile, web and moderation tools.
In development; no public URL is shown until one can be verified.
It started with study
Neqraw did not begin with the abstract idea of making yet another social app. It began with a more specific question: what happens if study and knowledge become the center of a community, rather than just a topic inside one?
The aim was to create a place where someone could enter through a subject, find people, start a group, publish a question and continue the conversation without leaving the product.
A community that holds together
Neqraw now presents itself as a social product around study and knowledge. The feed remains the entry point, but the current identity is clearest in the move towards groups, profiles and the spaces that let a community organise itself.
The product is therefore no longer limited to one screen: every surface has to help someone arriving understand where they are, who they are exchanging with and what they can do next.
What was actually built
Neqraw grew around three connected uses: enter through a subject or post, find context in profiles and groups, then keep the exchange going through posts, replies and messaging. Android and web served different situations; the Control Center kept the space governable.
The important part is not the number of surfaces. It is the move from a feed screen to a system where content, relationships and responsibility begin to hold together.
When use becomes a responsibility
As soon as a product lets people publish, create a group and speak directly to someone, it also has to account for what happens when usage goes wrong. Moderation, reports and sanctions therefore did not arrive as an administrative appendix; they gradually became part of how the product was designed.
The same logic applies to the sponsored feed and monetization. Before adding another surface, the product needs to know how it coexists with the trust the community gives the rest of the space.
Margin notes
Margin notes
Some decisions look different once you remember where they came from.
DECISIONS
When the product becomes a community
The feed was the entry point; the depth came from everything around it.
Make the feed an entry point, not the whole product
The feed gives people an immediate way into subjects and posts. It still needs to lead towards relationships, groups and conversations, otherwise a community becomes a sequence of cards to scroll past.
Give groups a real role
Groups add context: a subject, a purpose, a visibility and people who know why they are there. They turn an isolated post into a starting point.
Build mobile and web as one product
Android makes the everyday use direct; the web opens another surface for browsing, publishing and administration. The product logic has to stay coherent across both.
Treat moderation as a product surface
Reports, sanctions, admin tools and the Control Center appeared as the product gained depth. The sponsored feed and monetization were also treated as rules to frame, not a layer to add later.
CURRENT STATE
Neqraw — Now
Neqraw is in development. The captures shown here represent the current product across a mobile feed, groups and a web Control Center; they are not an archive of an earlier identity.
ARTIFACTS
From feed to social system
The current screens show how Neqraw connects discovery, community and governance.
