How do you build a social system when attention, access, and intimacy all need boundaries?
Nakupenda is an interest-graph social platform organized around Currents, with product-specific systems for messaging, community governance, long-form work, live audio, onboarding, and creator relationships.
OwnershipProduct design, interaction and state models, responsive UI systems, feature architecture, and implementation direction.
TEXTinRelationship stateMessaging with receiver-controlled boundaries
WHISPERSRole-aware live audioHost, co-host, speaker, listener
CONTROLGovernanceCommunity voting and appeal surfaces
01
Context / attention
The product is organized around meaning, not only popularity.
Nakupenda’s product source defines Currents as an explicit interest graph. People choose the spaces they want to participate in, and those choices shape onboarding, discovery, feed context, creation, and community identity.
This is a design decision about attention. Recommendation should be derivable from chosen context, not hidden behind a generic popularity loop.
Attention and participation flow
01ChooseSelect up to five Currents
02ContextCurrent and subgroup shape creation
03DiscoverFeed and explore follow explicit interests
04ParticipatePost, blog, message, or join live audio
05GovernBoundaries, roles, and community decisions
Decision evidence / CurrentsThe screen proves that interest selection is part of first-session product state, not a decorative topic picker.
02
TEXTin / boundaries
Messaging changes when the receiver controls access.
TEXTin is designed as relationship infrastructure rather than a generic message list. Conversation identity, privacy, message type, and access state belong to the thread.
01Boundary mode
After repeated unreplied messages, a receiver-configured boundary can make continued access explicit instead of allowing infinite social pressure.
02Private state
Secret inbox and whisper-style messages require protected entry, hidden notification behavior, and predictable expiry.
03Emotional identity
The conversation can carry theme and aura state without replacing the core clarity of sender, receiver, and message status.
04Capability honesty
Boundary charging, AI memory, and shared spaces remain active-testing areas until their backend contracts are complete.
Decision evidence / TEXTinThe interface makes the relationship boundary visible at the point where the next message changes state.UX-04A boundary should appear before the user crosses it.+
Access rules fail when they arrive as a surprise error. The interface should show who controls the boundary, why it exists, and what the next valid action is.
03
Whispers / realtime state
Live audio is a role system, not a single screen.
Whispers models ephemeral live rooms with explicit transitions between host, co-host, speaker, and listener. The UI separates moderation, stage control, speaking requests, gifting, listener rewards, and session retention.
Whispers speaking-state transition
DefaultListenerrequest to speak QueuePending reviewhost / co-host approves StageSpeakerdemote ReturnListener
Listeners can subscribe to room state, but publishing audio remains blocked until the role transition is approved.
Role
Voice
Moderation
Rewards
Retention
Host
Yes
Owns room
Can receive
Can end and download
Co-host
Yes
Stage support
Can receive
Policy-bound
Speaker
On stage
No
Can receive
Session-bound
Listener
By request
No
Can gift / react
Session-bound
The role-aware room UI is implemented. Some live payloads, gifting rules, snippet contracts, and retention mechanics remain incomplete backend work.
Decision evidence / WhispersThe screen is evidence of separate stage, listener, moderation, and participation states.
04
Community Control
Governance needs an inspectable decision trail.
Community Control gives members a structured way to review reported content, vote to keep or remove it, inspect the consensus, and enter an appeal path.
The product is intentionally more legible than opaque centralized moderation, but the current implementation is honest about contract gaps: the queue and skip flow are not fully backed, and appeal behavior still needs stable backend ownership.
GOV-01Participation is not the same thing as policy completeness.+
A voting surface can make a decision inspectable, but abuse prevention, eligibility, evidence handling, and appeal rules still need deterministic ownership behind the interface.
05
Blogs / monetization
Long-form work needs a different social contract.
Context
Every blog belongs somewhere.
Current and subgroup linkage keeps long-form work inside the interest graph rather than detaching it into a separate publishing product.
Access
Preview and entitlement are separate states.
Readers need a clear free boundary, locked continuation, and honest access state before monetization can feel fair.
Reliability
The article survives secondary failure.
Comments or entitlement hints can degrade without preventing the main article from rendering.
Direction
Living work, not a frozen post.
Versioning, collaboration, subscriptions, and voice comments remain planned until their APIs are verified.
Decision evidence / BlogsThe screen demonstrates that preview content and full entitlement are distinct reader states.
06
Design system
One visual system, different account intent.
Urbanist
A sharp operating typeface keeps dense social surfaces contemporary and compact.
Personal red
The personal account accent identifies action and active state without spreading into every surface.
Business green
Business accounts receive a separate accent while shared components retain the same architecture.
Theme layer
Semantic background and text roles support dark mode without rebuilding the component system.
The implementation uses a 4px/8px spacing grid, semantic background and text tokens, responsive layouts, and server components by default. Product-specific state is allowed to be expressive; navigation and action hierarchy stay familiar.
07
Outcome / learning
What the work proves.
Attention can be modeled as explicit user context through Currents.
Messaging UX improves when receiver-controlled boundaries and privacy states are first-class.
Live audio requires a role matrix, realtime transitions, and degraded states, not only an attractive room.
Community governance needs visible consensus and appeal paths, plus honest acknowledgment of incomplete policy contracts.
Screens are useful evidence only after the decision they prove is clear.
