Activity: Offline-First Testing

Objective

Test app resilience by simulating poor connectivity scenarios common in underserved communities.

Test Scenario

You're building a mental health crisis support app. Users may be in:

• Rural areas with spotty cell service
• Emergency situations with network congestion
• Low-income areas with limited data plans

Testing Framework

Step One: Baseline Online Test (5 minutes)

Use any social app on your phone with full internet:

1. Send a message to a friend
2. View recent posts/content
3. Access user profile
4. Search for content

Document: How long does each action take?

Step 2: Network Degradation Tests (15 minutes)

Test A: Airplane Mode Toggle

1. Turn on airplane mode
2. Try the same actions from Step 1
3. Turn on airplane mode, wait 30 seconds, turn off
4. Observe how app recovers

Test B: Slow Connection Simulation Use browser developer tools or network simulators:

1. Set connection to "Slow 3G"
2. Retry the same actions
3. Note loading states and error messages

Test C: Intermittent Connection

1. Toggle WiFi/cellular on and off every 10 seconds
2. Try to complete a critical action (like sending help request)
3. Observe user experience during connectivity gaps

Step 3: Crisis Scenario Simulation (5 minutes)

Imagine using the app during a mental health crisis:

• Every second feels critical
• Cognitive load is already high
• Technical problems create additional stress

Test questions:

• Can you access previously viewed supportive content offline?
• Are help resources cached locally?
• Does the app clearly communicate connection status?
• Can you queue messages to send when connection returns?

Observation Notes

Document for each test:

• User Experience: What does the user see/feel?
• Data Loss: What information gets lost?
• Recovery: How does the app behave when connection returns?
• Error Messages: Are they helpful or confusing?

Design Implications

Based on your testing, list three offline-first features that would improve crisis support:

1. Local Storage: What data should be cached?
2. Queue Management: What actions should work offline?
3. Status Communication: How should the app indicate connection state?

Success Criteria

A good offline-first crisis app should:

• Core content accessible without internet
• Clear offline/online status indicators
• Graceful degradation of features
• No data loss during connection interruptions

📤 Submit Your Work

Complete this activity and submit your work through the Activity Submission Form