TRACK 2 — WEB DEVELOPMENT

Web Development

Code. Scale. Innovate.

Build scalable web apps across frontend, backend, and full-stack. Innovate on SaaS products that can grow well beyond the hackathon.

01SNH-WD-01

StateSync Web: Websites That Resume Themselves

Problem Statement

Modern web applications lose context whenever users:

Change devices
Lose connectivity
Close browsers
Switch tabs
Encounter crashes
Return after several days

Build a web platform capable of reconstructing a user's exact working state rather than simply restoring saved data.

Challenge

Develop a web application where the user's complete operational state can be reconstructed across devices.

State may include:

UI position
Unsaved work
Workflow stage
Selected components
Temporary calculations
Navigation state
Permissions
Partially completed actions

Example

A user:

Starts designing a dashboard on Laptop Aloses internetopens Tablet B.

The system should reconstruct:

“You were editing this dashboard, at this exact workflow stage, with these unsaved changes.”

Expected Output

A functional cross-device web application demonstrating:

State capture
State synchronization
Conflict resolution
Cross-device recovery
Offline/online transition
Restoration of unfinished workflows

02SNH-WD-02

WebMorph: Interfaces That Reconfigure Around User Intent

Problem Statement

Most web applications have static layouts.

But the optimal interface for a user changes depending on:

Task
Device
Available screen space
Interaction history
Urgency
User workflow
Accessibility requirements

Challenge

Build a web platform whose interface dynamically restructures itself according to the user's current objective.

The system should not merely resize components responsively.

It should alter:

Information hierarchy
Component arrangement
Navigation
Interaction sequence
Density
Controls

based on inferred task intent.

Example

A dashboard normally displays 20 widgets.

When the user enters:

“Investigate today's failed transactions.”

The interface dynamically restructures itself around:

Failed TransactionsRoot CauseRelated EventsResolution

Expected Output

A working application demonstrating:

Intent detection
Dynamic UI generation
Component prioritization
Task-specific navigation
Real-time interface transformation
User feedback and adaptation

03SNH-WD-03

DataShadow Web: Zero-Trust Personal Data Architecture

Problem Statement

Traditional web applications often send user data to servers simply because the architecture was designed around centralized processing.

Challenge the assumption.

Build a web application where sensitive computation happens locally whenever possible, while the server receives only the minimum representation required.

Challenge

Develop a browser-first architecture capable of:

Identifying sensitive fields
Classifying computation
Deciding local vs remote execution
Transforming data before transmission
Maintaining functionality under restricted connectivity
Reconstructing server-side results without exposing raw sensitive data

Example

Instead of sending:

Complete personal profile

the browser computes a required feature locally and sends:

Privacy-preserving derived representation

Expected Output

Teams should demonstrate:

Sensitive-data classification
Local computation
Remote computation
Automatic execution decisions
Data minimization
Functional results without unnecessary raw-data transmission

04SNH-WD-04

WebPulse: Predictive Network-Aware Application

Problem Statement

Web applications traditionally react to network conditions:

Network becomes slowapplication responds slowly.

Build one that anticipates network degradation before it happens and restructures its own operation.

Challenge

Develop a web application capable of predicting short-term connectivity conditions and proactively modifying:

Resource loading
API calls
Synchronization frequency
Media quality
Data compression
Caching
Computation location

Example

The system predicts:

“Connectivity degradation likely within 15 seconds.”

It proactively:

Downloads required resources
Queues non-critical requests
Compresses future payloads
Switches to offline-first execution

Expected Output

A working application demonstrating:

Network monitoring
Connectivity prediction
Proactive resource management
Adaptive synchronization
Offline capability
Measurable improvement under simulated network degradation

05SNH-WD-05

WebIntentOS: Intent-Based Web Navigation

Problem Statement

Current websites require users to understand the website's information architecture.

Users think in goals:

“I need to compare these three products.”

“Find why this payment failed.”

“Prepare this report using last month's data.”

But websites expect:

Click menuopen pagesearchfilternavigateexport.

Challenge

Build an intent-native web application where users express an objective and the platform dynamically constructs the shortest valid interaction workflow.

The system must not simply be a chatbot overlay.

It should manipulate the actual application state.

Required Capabilities

The platform should:

Understand user intent.
Convert intent into executable application actions.
Validate permissions.
Construct a workflow.
Execute permitted actions.
Detect failures.
Recover or request clarification.
Provide an auditable action trail.

Expected Output

A functional web application demonstrating:

Intent interpretation
Workflow generation
Permission validation
Application/API execution
State verification
Failure handling
Action history