Value Proposition, CAS and Smart Features

Value Proposition

Note: Taken from Sprint 1 deliverable

SENECApp helps university students discover, create, and grow student communities in one place.

Students who want to join a group can easily find communities based on their interests instead of depending on scattered information from social media, chats, or word of mouth. Students who want to create a new group can also share their idea, find people with similar interests, and measure interest before spending time on a formal registration process.

Unlike alternatives such as WhatsApp groups, Instagram pages, or informal messages between students, SENECApp brings the discovery and creation of university communities into one dedicated platform. This makes groups easier to find, helps new initiatives become visible, and gives students a simpler way to connect with people who share their interests.

How do the smart features generate value

First, let's take a look of our proposed smart features:

Discovery and growth

Smart feature	Data and processing	Value generated
Group recommendations	Similarity between the student's profile/behavior and the members or event history of each group	Converts passive browsing into membership; solves the "I didn't know this group existed" case.
Personalized event feed	Interests declared at onboarding & implicit signals (views, saves, RSVPs) + program/faculty; content-based matching against event tags	The student sees a short, relevant list instead of a full catalogue. Directly attacks the discovery cost that motivates the app.
Trending and popularity ranking	Aggregated views, saves and RSVPs over a time window	Social proof lowers the decision cost of attending alone, and surfaces groups and events that are gaining traction before they happen.
Smart notifications	Per-user engagement history (when they open the app, which categories they act on)	Higher attendance conversion with fewer notifications. Value is as much in what is not sent as in what is.
Organizer analytics	Event-level funnel: impressions -> saves -> RSVPs -> attendance	Value for the supply side of the platform. Groups that see their reach keep publishing, which keeps the catalogue alive for students.

Creation

Smart feature	Data and processing	Value generated
Interest-demand estimation	Proposed group's tags matched against declared interests and behavior across the student base	The founder sees whether demand exists before investing in formal registration, the measurement the value proposition promises.
Co-founder / early-member matching	Similarity between the idea's profile and students with overlapping interests and no existing group in that space	Turns an idea into a cohort, which is the actual bottleneck in starting a group.
Idea deduplication	Semantic similarity against existing groups and pending ideas	Prevents the fifth photography club; routes the student into something already alive.

These features generate value because the scarce resource for a student is attention and free time between classes, not information. The discovery features convert raw catalogue data into a ranked, short answer to "what should I do today?", which is the job the user wants the app for. The creation features answer a different question, "does anyone else want this, and who?", which no amount of browsing can answer and which WhatsApp and Instagram cannot support at all.

How do the CAS features generate value

Now, let's review our CAS features:

Context signal	Source	Adaptation	Value generated
Location on campus	GPS / coarse location	Prioritize events happening nearby in the next hours; show walking distance to the building	Turns interest into attendance, a relevant event three buildings away at the wrong time is not actionable.
Time of day and academic calendar	System clock, term calendar	Surface activities that fit the gaps in a typical schedule (lunch block, end of day); suppress finished events	Respects the real constraint on attendance: available time, not interest.
Connectivity state	Network state / connectivity manager	Serve cached content and queue writes when connectivity drops; degrade images before text	The app remains usable in campus dead zones and on limited data plans. Reliability is itself value for a discovery app used while walking.
Draft state and connectivity	Local storage, network state	Persist the idea draft locally and sync when connectivity returns	Ideas get floated in the dead minutes between classes, exactly where campus connectivity is worst.
Battery and data saver mode	Battery / power manager	Reduce prefetching and background refresh under low battery or data saver	The app does not become the reason a student's phone dies mid-day.
Device state during class	Calendar / do-not-disturb, time	Hold non-urgent notifications until a break	Avoids the interruption that would make the student disable notifications entirely, protecting the channel the app depends on.

These features generate value since the CAS layer answers "what can I actually attend, right now, with this phone, on this connection".

Additional information for group use

We know these are not required but we are stating them for internal reference during the development of the app.

Mapping to the CAS reference architecture

Layer	In SENECApp
Sensors	Location, connectivity state, battery, clock, in-app interaction events
Storage	Local cache for offline browsing and idea drafts; backend storage for the group and event catalogue
Processing	Ranking and recommendation, demand estimation, trending computation, notification timing, analytics aggregation
Actuators	Notifications, adaptive prefetching, reduced-quality media under constrained conditions
GUI / user interaction	Adaptive feed, contextual "near you / starting soon" section, offline indicators

The two layers compose: sensors and GUI make SENECApp context-aware, and the processing layer is what makes it smart. Removing the processing layer leaves a working but generic group and event list; removing the context layer leaves good recommendations the student cannot act on.

Constraints this addresses

• Device and context constraints: intermittent campus connectivity, limited data plans, battery pressure during a full academic day.
• Fragmentation: feature degradation is tied to capability checks rather than assuming a high-end device.
• Attention constraints: short sessions between classes, usually one-handed while walking.