How jagadish-pattanaik/ao-classes works
Project type and purpose
• This is a single-module Android mobile application (“AO Classes”) built with Java and Gradle.
• Its purpose is to provide “all in one online teaching” by integrating multiple online-meeting platforms, whiteboards, question banks, PDF tools, reminders, and resource libraries into one APK (<10 MB).
File structure
• Top-level Gradle files (build.gradle, settings.gradle, gradle-wrapper) define a standard Android project.
• The app/ module contains:
• src/main/java/com/jaguweb/aoclasses/… – hundreds of Activity classes, utility and controller classes (e.g., BluetoothController, RequestNetworkController).
• src/main/res/layout/ – XML layouts matching each Activity.
• AndroidManifest.xml – declares Activities and permissions (Bluetooth, Internet, camera, storage).
• No backend code or server components—this is a purely client-side monolithic mobile app.
README for additional insights
• Features list implies integrations with external services: meeting platforms (Zoom, Teams, Jitsi, etc.), whiteboard tools, file scanning & PDF conversion, question banks and e-book resources.
• No explicit data-persistence layer described; likely using in-memory or simple storage (SharedPreferences or files) via FileUtil and RequestNetwork.
Capturing essential architectural elements
• Don’t list every Activity separately; group by feature area.
• Android Manifest permissions as a call-out.
• In-app routing: how MainActivity links to sub-features via Intents.
• Detail the integration points for network and SDK calls.