How aayushkrgupta/pulse5g works
Pulse5G is a cross-platform incident-monitoring app. Its visible workflow is dashboard polling and live alert updates from an edge service, with incident history saved locally and camera streaming exposed through the camera UI. The README also describes geofencing, push notifications, Firebase, and edge processing, but the sampled source does not establish their implementation or wiring; those capabilities are not represented as implemented components here.
Main entry points: _layout.tsx Tab navigation · api.ts HTTP API · dashboard.tsx Dashboard · incidents.tsx Incident history
Components 14
Mobile interface
- App entry
App.tsx - Initial redirect
app/index.tsx - Tab navigation
app/(tabs)/_layout.tsx - Camera screen
app/(tabs)/cameras.tsx - Network screen
app/(tabs)/network.tsx - Video stream
src/components/LiveVideoStream.tsx
Incident monitoring
- Dashboard
app/(tabs)/dashboard.tsx - Incident history
app/(tabs)/incidents.tsx
Edge connectivity
- HTTP API
src/services/api.ts - Alert socket
src/services/websocket.ts - Endpoint config
src/services/config.ts
Local state
- Secure storage
Other components
- Operator
- Edge service
Connections 19
- Operator → App entry: opens
- App entry → Initial redirect: loads
- Initial redirect → Tab navigation: redirects
- Tab navigation → Dashboard: routes
- Tab navigation → Incident history: routes
- Tab navigation → Camera screen: routes
- Tab navigation → Network screen: routes
- Dashboard → HTTP API: fetches latest
- Dashboard → Alert socket: subscribes
- Dashboard → Incident history: opens history
- Incident history → HTTP API: fetches latest
- Incident history → Secure storage: reads/writes history
- Camera screen → Video stream: renders
- Video stream → HTTP API: gets stream URL
- HTTP API → Endpoint config: reads endpoints
- Alert socket → Endpoint config: reads endpoint
- HTTP API → Edge service: requests data
- Alert socket → Edge service: connects
- Video stream → Edge service: loads stream