Why Was Wazaif & Dhikr Counter Created?
Purpose, Core Value & Comprehensive Testing Guide for Google Play Beta Program Testers.
“To make worship easier, maintain reliable recitation records, and help track spiritual practices in an organized manner.”
It is not intended to replace the act of worship. It is a digital tool designed to support the person performing it.
Why Was Wazaif & Dhikr Counter Created?
Wazaif & Dhikr Counter was created with a simple purpose: to make daily recitation and spiritual practice easier to manage, record, and track through a reliable digital system.
The application brings commonly performed practices such as Wazaif, Durood, Tasbeeh, and Quran reading into one organized platform, while providing users with a practical way to maintain their recitation records and progress.
For individual users, the goal is to make personal recitation tracking simple and meaningful. For Madrasas and organized groups, the platform is designed to support collective recitation records, history, and structured tracking.
What Is the Core Focus?
Our development priorities focus strictly on user value and spiritual organization:
Simplicity
Clean, intuitive flow for all ages.
Accuracy
Flawless counting and zero data loss.
Reliable Records
Comprehensive history & progress logs.
Distraction-Free
Zero popup ads or intrusive elements.
Quran Reading
Authentic text & Surah/Para navigation.
Offline First
100% functionality without internet.
Madrasa Tracking
Group recitation & collective records.
Data Safety
Strict user privacy & account isolation.
What Should Beta Testers Focus On?
Beta testing should not be limited to checking whether a button works. Every tester should use the application as a real user would use it in daily life.
1. Accuracy
Check whether every count, record, and progress value is completely accurate.
- Increase the counter repeatedly.
- Close and reopen the application.
- Check whether the count remains correct.
- Test reset and other counter actions.
- Verify that history reflects actual activity.
2. Real-World Usability
Use the application naturally rather than testing only individual buttons. Ask yourself:
Check navigation flow, font readability, button touch targets, menus, forms, and overall user experience.
3. Quran Reading Experience
Test the Quran section carefully on various devices. Check:
- Arabic text rendering and diacritics.
- Surah/Para navigation and quick jumps.
- Reading position saving & bookmarking.
- Smooth scrolling and page/reading transitions.
- Font readability across Urdu and English interface text.
- Responsive layout across different screen sizes.
4. Offline Experience
Turn off your internet (Wi-Fi & Mobile Data) and continue using the application. Check whether:
- The application opens normally.
- Counters continue working seamlessly.
- Existing recitation records remain available.
- Quran reading remains accessible.
- Actions do not unexpectedly fail.
- Data is preserved safely when connectivity returns.
The application's architecture is specifically designed around offline-first local persistence with synchronization capabilities, so offline behavior is an important part of testing.
5. Data & Account Safety
Test account isolation behavior carefully. If possible, test this sequence:
Verify that User B cannot see User A's private counters, history, settings, or account information. Also report anything that appears to belong to another account.
6. Language & Display
Test both Urdu and English interfaces, as well as Arabic Quran text. Look for:
- Incorrect Urdu grammar or translation.
- Broken Arabic characters or fonts.
- Text overlapping or wrong alignment.
- RTL (Right-to-Left) and LTR layout issues.
- Cut-off text or incorrect numbers.
- Buttons becoming too small or misaligned on larger font sizes.
7. Stability
Use the application normally for an extended period. Please report:
- App crashes or sudden closures.
- Screen freezing or lagging animations.
- Unexpected logout or session loss.
- Data disappearing after backgrounding app.
- Repeated taps causing unexpected behavior.
- App behaving differently after reopening.
8. Madrasa / Group Features
If testing a Madrasa or Group account, test from an administrator or teacher's practical perspective. Check whether:
- Group recitation records are clear and understandable.
- Assigned Wazaif are displayed accurately to students.
- Recitation history and reports are useful and correct.
- Leaderboards show expected information.
- Madrasa-specific information remains strictly separate from individual personal accounts.
“Please don't test only what the application is supposed to do. Test what a real user might actually do.”
Try normal actions, unusual actions, repeated actions, offline usage, account switching, closing and reopening the app, entering unexpected information and navigating through different sections.
If something feels confusing, inaccurate, slow, inconsistent or simply “not right”, report it — even if you are not sure whether it is technically a bug.
What Should Be Reported?
To help our engineering team fix issues quickly, please structure every bug report with these 5 details:
“I opened the Durood counter, increased the count 20 times, closed the application and opened it again. The counter showed 19 instead of 20.”
“Counter has a problem.”
The Objective of Beta Testing
The objective is not to prove that the application works. The objective is to discover anything that could prevent a real person, student, teacher, madrasa administrator, or individual user from using the application comfortably, accurately, and reliably.