FeedbackGo

FeedbackGo is a lightweight Expo/React Native Android application that opens the college ERP in a WebView. Students complete the ERP's existing password/OTP login themselves. After login, they can select a rating preference and use Complete My Feedback to start an on-device feedback workflow.

Download website: https://dev-rohit-gupta.github.io/auto-feedback/

How it works

• A floating native menu offers Excellent, Average, Poor, and Random rating preferences.
• The app visits the available ERP session, feedback-type, and subject selections using an explicit traversal cursor. It waits for ERP postbacks and reloads rather than using arbitrary delays.
• For recognized forms, it fills supported dropdown/radio ratings and verifies the selected answers.
• Academic feedback uses the known Save(Draft) and Final Submit controls. Direct Facilities-style forms use their own Submit control. Saves/submissions are counted only after recognized ERP confirmations.
• Explicit already-completed messages and branches where the ERP does not expose an editable form are tracked separately. Missing forms are not treated as successful submissions.
• A native progress overlay shows the current ERP selection path and the verified question count for the current form. The finished view uses a separate results summary rather than showing stale loading/progress text.

Diagnostics and privacy

The Share diagnostic report action is available from the floating menu and finished results screen. Reports contain a bounded, in-memory list of predefined technical event names and sanitized status/index metadata; no raw ERP URLs, passwords, OTPs, student identities, cookies, or feedback answers are recorded by this logger. Public builds do not print detailed diagnostic events to the device console. Reports are only shared when the user explicitly chooses to share them.

The WebView retains the ERP login session on the device. The app does not send student credentials to a FeedbackGo server.

Project structure

• App.tsx: WebView session, native application coordination, ERP reload/postback signals.
• src/automation/: traversal coordinator contracts, rating strategies, feedback progress and result presentation policy.
• src/erp/: ERP selectors, injected scripts, typed bridges, form/status inspection, save/submit verification.
• src/components/: native feedback menu, progress/result overlay, alerts, login gate, offline demo UI.
• src/diagnostics/: bounded, sanitized, share-on-demand diagnostic report.
• src/config/: features, ERP origin, brand settings.
• src/theme/: device-theme-aware native colors.
• tests/: isolated automation, ERP bridge, submission, and UI presentation tests.

Local development

npm ci
npm test
npx tsc --noEmit
npx expo start -c

The current Expo configuration references expo-splash-screen; before your first APK build, run npx expo install expo-splash-screen if it is not already installed. Use EAS Build for a signed, installable APK and test the native splash with a standalone build, not only Expo Go.

Release readiness

See RELEASE-CHECKLIST.md for Android signing, ERP live-flow, theme/accessibility, diagnostic privacy, and GitHub Releases verification steps.

Release limitation: WebView automation can fail when the ERP changes its structure, labels, validation rules, or confirmation behavior. The full real-ERP sequence and public APK have not yet been verified from this environment. Only publish a stable release after validating the exact live save and final-submit behavior on an authorized test account. The app is independent and is not an official ERP product.