How theandroguy/plinkz works
Plinkz is a single-module Android application (Gradle multi-file setup, but only one app module) whose purpose is: capture URLs via Android’s Share sheet, persist them locally for offline access, and present/manage/share them in a list UI.
• Android entry points (Activities, Dialog)
• Data layer (Room DB: Entity/DAO/Database)
• UI layer (RecyclerView + Adapter + XML layouts)
• OS integrations (Android Sharesheet intents, browser intents)
• Build/release (Gradle, APK/AAB outputs) as a side note
File-structure-driven component identification
From the tree, the main components map cleanly:
Data / Persistence (Room)
app/src/main/java/com/tushar/plinkz/Modal/
• Link.java (Room Entity model)
• LinkDao.java (DAO: CRUD queries)
• AppDatabase.java (RoomDatabase singleton)
Resources (UI assets)
app/src/main/res/
• layout/* (activity screens, list row, dialogs)
• menu/toolbar_menu.xml (actions: search/share/delete/etc.)
App configuration & build
• AndroidManifest.xml (declares Activities, intent-filters, share handling)
• app/build.gradle.kts, root build.gradle.kts, settings.gradle.kts, libs.versions.toml (dependencies and versions)
• app/release/* (prebuilt artifacts; not part of runtime architecture but relevant to “deployment”)
User actions
• Open in browser (implicit intent)
• Share saved link (share intent)
• Delete/update (DAO writes)
Android OS / External Apps
• “Other apps (YouTube/Chrome/Instagram)”
• “Android Sharesheet / Intent Resolver”
• “Browser (Chrome Custom Tabs / external browser)” (if used; otherwise generic “Browser app”)
App (Plinkz)
By package/folder:
• Entry/Navigation
• MainActivity
• Share Capture
• ShareActivity (+ intent-filter in Manifest)
• SaveLinkDialog / activity_save_link_dialog.xml / dialog_save_link.xml
• Link Management UI
• LinkViewRecyclerActivity / LinkListActivity
• LinkAdapter + link_list_item.xml
• Toolbar menu actions (search/share/delete/open)
• (Optionally) “UI Resources” bubble pointing to layouts/drawables/themes
Data Layer
• Room:
• AppDatabase
• LinkDao
• Link (Entity)
• Under that: “SQLite (on-device)” (Room sits atop SQLite)
• Intents coming in/out (Share/Open/Share)
• DB reads/writes (DAO calls)
• UI rendering (Adapter binds Link list)
For maximum accuracy without overcomplicating:
External / OS interactions
• External App → Android Sharesheet → ShareActivity
• Link list/detail → “Open in browser” intent → Browser App
• Link list/detail → “Share” intent → Android Sharesheet → External Apps
UI ↔ Data interactions
• ShareActivity → AppDatabase/LinkDao (INSERT Link)
• ManualSaveLinkActivity → LinkDao (INSERT Link)
• LinkViewRecyclerActivity/LinkListActivity → LinkDao (SELECT list, maybe DELETE/UPDATE)
• LinkAdapter consumes List<Link> (data binding)
In Android, the Manifest is architecture:
• AndroidManifest.xml as configuring:
• Activities
• Intent filters (especially share)
High-level runtime architecture (single page)
OS/external apps ↔ Plinkz Activities ↔ Room/SQLite
External App → Sharesheet → ShareActivity → SaveLinkDialog → DAO → DB → UI refresh
UI composition mini-map (optional but accurate for Android)
Activities → associated XML layouts and key widgets (RecyclerView row layout + menu)