Complete case records
Store title, side, plaintiff, defendant, address, case number, court, hearing dates, issue, priority, status, notes, document sections, reminders and financial entries.
Complete feature catalogue
Visible workflows, automatic background behaviour, platform boundaries and security-sensitive controls—matched against the Flutter 2.4.1 source.
Case Diary
Case details remain connected to dates, reminders, money, team identity, history and share output.
Store title, side, plaintiff, defendant, address, case number, court, hearing dates, issue, priority, status, notes, document sections, reminders and financial entries.
Use Running, Disposed, Disengaged and Draft states, with controlled close, reopen and final-status actions.
Open All, Running, Today, Tomorrow, Overmorrow, Next Week, Date, Court Name, Expired, Due Money, Updated, Reminder, Disposed, Disengaged or Draft views.
Show, hide and reorder quick filters so the diary matches the chamber’s working style.
Search title, party side, plaintiff, defendant, address, court and assigned team. Bangla/English digits, leading zeroes and common case-number separators are normalised.
Typing while another quick filter is active automatically returns to All, reducing the chance that a matching case remains hidden.
Maintain court groups and court names, then browse cases by court or date.
Keep next dates, issues, reminders and chronological activity instead of replacing the earlier trail.
Move a case to another court while preserving the history of the transfer.
Review edits, dates, notes, payments, status changes and other case activity in one ordered history.
Connect running matters, review related cases and create grouped sharing output.
Generate individual or grouped case cards, images and PDF output with chamber, advocate and operator identity rules.
Dashboard, reports and tasks
The dashboard and To Do system surface action without losing the underlying case trail.
See today’s cases, next dates, overdue tasks, urgent reminders, recent legal notes and recently viewed material.
Create a cause-list view grouped by court and export it as PDF.
Review received, due, expense, balance and client-wise summaries.
Record received, due and expenses; resolve dues as paid or declined; retain source, receipt and edit/delete actions.
See Google Drive connection, latest backup, chamber live-sync state and pending work.
The app can display a chamber-setup reminder when identity or team configuration is incomplete.
Create tasks with priority, date/time and optional case connection.
Separate Overdue, Upcoming and Completed work.
Task edits are automatically saved after a short pause, reducing repeated manual save actions.
Completed tasks wait briefly before moving, giving a 10-second opportunity to undo an accidental completion.
A case reminder can create or update its linked To Do item and local notification.
Completion timestamps and unique event identities help preserve concurrent completion/reactivation changes during sync.
Chamber collaboration
The website now uses the exact active app roles—not retired Owner, Senior Lawyer, Accountant or Read-only labels.
Use Admin, Advocate, Apprentice Advocate, Chamber Clerk and Legal Assistant. Legacy labels are migrated to the nearest current role.
Only a licensed Advocate can be the case Advocate. Apprentice Advocate, Chamber Clerk and Legal Assistant may be assigned as Assistant.
Admin manages chamber members, cases and team controls but is not silently stored as the case advocate.
Switching a device profile to Admin requires PIN or biometric approval.
Previous profile, next profile, device, time and approval method are recorded and included in encrypted backup/sync.
Admin can apply supported assignment changes across active cases with rollback safeguards if the operation fails.
Create or reuse a chamber Drive folder, invite a member and join through an invitation containing the folder reference and chamber key.
Membership and folder access are verified before a join is committed; failed joins are rolled back.
Review members and sync history, revoke or reinvite access, and respond to a lost device.
Rotate the chamber key after revocation or a suspected device compromise.
Sharing is blocked when required chamber identity or case authority is incomplete.
Shared case output can show chamber/advocate identity at the top and the active operator in the footer.
Decisions and Laws
Google identity protects legal-library access while the daily diary, tasks and calculators remain usable without Google sign-in.
Diary, To Do and calculators work without Google. Decisions and Laws use Google identity for authorised library access.
Legal-library metadata is stored in a SQLCipher database with a random 256-bit key held in secure platform storage.
Search locally indexed titles, excerpts and citations after metadata has been downloaded.
The first snapshot is paged and can resume through saved page/cursor progress.
After the first snapshot, the app requests changed metadata and deleted IDs, applying each delta atomically.
Legal updates can run at launch, foreground/resume, manual refresh, connectivity restoration and an in-process periodic check.
Overlapping sync requests are coalesced; Retry-After, bounded exponential backoff and jitter are used for transient failures.
Use All, Read, Unread, Notice, Favourite, Folder and Category views.
Organise favourite material into folders, add legal notes, review notices and return to recently viewed items.
Download a full item only when needed. Revision checks keep a valid cached copy readable when the network check fails.
Read citations, case summary, full judgment and detected legal sections with a table of contents.
Use the built-in compatibility route or add a personal Google Cloud Translation API key stored in secure storage; its project quota and billing belong to the key owner.
Create reviewable legal PDF/share output with controlled file naming and formatted judgment text.
Passive and automatic features
These behaviours run when their prerequisites are met. Android may defer background work during severe battery or storage constraints.
Case-data changes mark backup state dirty. The app coalesces rapid edits, normally waiting about seven minutes after the last change and no more than about thirty minutes after the first unsaved change.
Important pending changes can be flushed when the app moves to the background or another critical lifecycle event occurs.
When enabled and connected, an encrypted local backup is scheduled from around 1:00 AM device time before upload.
Android WorkManager keeps daily, dirty-snapshot and pending-upload jobs persistent across app-process termination and device reboot.
A backup created while offline remains in a durable local queue and resumes when an allowed internet connection returns.
Background backup and chamber sync reuse a saved Google session and never open a sign-in window automatically; revoked access requires manual reconnect.
Encrypted files use resumable upload with confirmed offsets and 1 MiB chunks, so a transient failure does not require restarting the entire transfer.
SHA-256, deterministic backup identity and Drive app properties validate the queued file and help prevent duplicate uploads.
Transient upload failures retry from about ten minutes with exponential backoff and jitter capped at six hours. Storage-full and reconnect-required states remain visible for user action.
Successful automatic Drive backups are cleaned according to the app’s current five-day automatic-backup retention policy; manual exports remain user-managed.
The chamber live channel pings and reconnects automatically. Encrypted Drive baseline/patch files provide a fallback path.
Same-field and delete-versus-edit collisions preserve local and remote versions; the app does not silently overwrite one side.
Case and task reminder notifications are scheduled or rescheduled when their source record changes.
The app can re-lock after roughly 30 seconds in the background when launch lock is enabled.
Release update metadata is Ed25519-signed; downloaded artifacts are checked over HTTPS with SHA-256 and Windows installer signature checks before use.
Generated temporary files are cleaned through the app’s file service rather than being intentionally kept as permanent records.
Settings and platform experience
Language, appearance, lock, backup, update and identity controls are available from the app settings.
Switch the application language between English and Bangla.
Choose a fixed appearance or follow the operating system.
Use mobile bottom navigation or desktop navigation and Ctrl+1 through Ctrl+5 section shortcuts.
Configure language, chamber identity and initial working information on first use.
Set a PIN, optional supported biometrics and launch-lock behaviour.
Review security-sensitive and chamber-related audit information.
Connect Drive, view last backup state, export/import encrypted JSON and view/copy or enter a recovery key.
Check the signed application update channel from settings.
View the published access period and future plan information.
Open the built-in developer and app information page.