Dhikr One.
Feel every count.
A premium wearable digital tasbih concept combining a color E-Ink display, tactile haptic language, reliable offline counting, and a privacy-conscious companion app.
Concept report · Prepared October 2026 · Visuals and specifications are illustrative, not a validated product.
A new category, not just another counter
The opportunity is a refined, distraction-free dhikr experience—not a long feature checklist.
See less. Feel more.
Count pulse
A soft, optional pulse after a successful button press. Haptic intensity and per-count feedback are configurable.
Cycle marker
A recognizable double pulse at a selected milestone, such as 33 or 99.
Goal reached
A distinct gentle pattern when a user-defined session target is reached, without loud sounds or bright animations.
Quiet privacy mode
Disable haptics, dim the display, hide the count, and keep the device discreet when desired.
Illustrative haptic pattern language
Conceptual timing only—not actuator measurementsCompact, modular, dependable
Conceptual block diagram. Final pin assignments, power rails, display interface, charging protection, and PCB layout require component datasheets and engineering validation.
Candidate component stack
- MCU/BLE: Nordic nRF52840-class platform for development; custom compact PCB later.
- Haptics: LRA actuator with a driver such as TI DRV2605L, after checking package and supply constraints.
- Display: small SPI color E-Ink module; verify dimensions, partial refresh, refresh time, and availability.
- Input: mechanical tactile switch with robust debounce and long-press reset protection.
- Power: protected rechargeable Li-Po, charging IC, battery measurement, and low-battery behavior.
Design constraints to resolve
- Ring packaging is especially difficult; finger-loop gives more room.
- Display refresh can be slow; counting must never wait for the screen.
- Frequent full-screen refreshes may affect energy and user experience.
- Haptic feel depends on actuator mounting and skin contact.
- Battery capacity, charging, sealing, and antenna performance must be tested in the final enclosure.
Button, touch, haptics & color E-Ink
The controls should feel immediate like a phone, while preserving the reliability and simplicity of a dedicated tasbih.
Primary tactile count button
Use a low-profile mechanical switch or sealed dome switch as the primary count input. It gives clear physical confirmation and works without looking at the device.
- Short press: add exactly one count.
- Long press: open a safe action menu; never reset immediately.
- Double press: optional undo only if users can learn it reliably.
- Debounce in firmware; ignore switch bounce and impossible press rates.
- Require a confirmation step for reset to prevent accidental data loss.
Recommendation: keep a physical button as the dependable primary input, even if touch controls are added.
Capacitive touch surface
A touch-sensitive strip or pad can provide a phone-like interaction for secondary controls. It detects a finger through a change in capacitance rather than a mechanical click.
- Tap: wake the screen or switch the information view.
- Swipe: optional screen navigation, only if it is comfortable on the final form factor.
- Touch-and-hold: enter settings or lock mode.
- Use touch for navigation, not the only counting input, until reliability is proven.
- Validate performance with dry/wet fingers, gloves if relevant, sweat, and charging noise.
Candidate: MCU-integrated capacitive sensing or a dedicated touch controller. Select after testing electrode geometry and enclosure materials.
Haptic feedback: control loop
When a valid press is detected, firmware should update the count first, persist the new state, then trigger the selected haptic pattern. Display refresh and Bluetooth must not block this path.
- Use an LRA for controlled, crisp patterns; compare it with a smaller ERM motor in physical prototypes.
- Provide haptic profiles: Off, Count, Milestones, and Custom.
- Use a short confirmation pulse, a distinct milestone double-pulse, and a separate completion pattern.
- Throttle or disable per-count pulses to conserve energy.
- Test actuator placement, vibration transmission, acoustic noise, and perceived strength on different fingers.
Color E-Ink display pipeline
Use the display module's supported controller and waveform behavior rather than assuming every panel supports fast partial refresh.
- Choose a panel only after confirming active area, resolution, color set, interface, driver support, refresh time, and supply continuity.
- Render the count in high-contrast black on a light background; reserve color for labels, targets, and status.
- Keep the count state authoritative in firmware, independent of what is currently visible.
- Use partial refresh only if the chosen panel supports it well; otherwise batch visual updates while haptics remain immediate.
- Test ghosting, full-refresh flicker, low-temperature behavior, and readability in sunlight.
Recommended event sequence
Designed to keep counting immediate even when E-Ink refresh is slowA real companion app—not just Bluetooth pairing
Pair and configure
On first setup, the app discovers the device, pairs securely, lets the user choose language, dhikr preset, target count, haptic profile, display theme, and left/right-hand preferences.
Count locally, sync safely
The wearable counts while offline. Each committed event or session snapshot includes a session ID, sequence number, count, and device timestamp where available. Reconnect logic reconciles state rather than blindly adding totals.
History and privacy
Show session totals, custom targets, and trends without presenting them as a measure of faith. Keep data on-device/phone by default; make account-based backup optional and explain what is uploaded.
Suggested app screens
Live device
Current count, battery, connection status, sync status.
Controls
Haptics, touch gestures, target milestones, display palette.
Dhikr library
Saved presets, Arabic text, optional transliteration and translation.
History
Session log, daily/weekly summaries, export and optional backup.
| Connection state | Expected behavior |
|---|---|
| Phone connected | Send updates in the background; show connection and sync status without making every count depend on the phone. |
| Phone out of range | Continue counting and saving locally. Queue the necessary session updates for later synchronization. |
| Phone reconnects | Exchange device/session identifiers and sequence state; reconcile missed events without duplicate counts. |
| Low battery / reboot | Save the count safely, communicate low battery, and restore the last committed session after restart. |
Reliable offline. Better when connected.
Firmware
Count state machine, button debounce, milestone rules, display scheduler, haptic scheduler, battery monitoring, and crash recovery.
Bluetooth protocol
Services for count state, session settings, battery status, firmware version, and sync. Use authenticated pairing and predictable reconnection.
Mobile app
Flutter or React Native are candidates for iOS and Android. Start with local storage; add accounts or cloud backups only if users want them.
Recommended software behavior
Priority labels are qualitative planning decisions, not measured performance scores.
From concept to pilot in 18 weeks
Validate form and display
Interview 10–20 prospective users; compare ring, finger-loop, and wrist designs; source display candidates; measure module dimensions and estimate power.
Gate: confirm a suitable display can fit the intended design.Prove electronics
Connect BLE development board, display, switch, and LRA. Implement counting and targets; measure refresh time, current consumption, and vibration quality.
Gate: prove the key interactions work together.Custom PCB and enclosure
Design a compact PCB, print fit-test enclosures, integrate charging and battery protection, and implement sleep and count recovery.
Gate: comfortable wearable with repeatable counting.Pairing and synchronization
Build BLE pairing, settings, targets, and session history. Test disconnects, resets, low battery, and duplicate-event handling on iOS and Android.
Gate: app and device remain consistent through interruptions.Validate and refine
Produce a small engineering batch; test comfort, battery life, charging, durability, and water resistance; collect user feedback and manufacturing quotes.
Gate: decide whether to invest in tooling and production.Timeline assumes a focused team with embedded, mechanical, and mobile expertise. Component sourcing and PCB revisions can extend it.
Indicative prototype investment
Planning ranges only—not supplier quotes. Excludes production tooling, certification, and commercial launch.
Cost range by workstream
Approximate total for a focused outsourced engineering effort.
Cost controls
- Start with off-the-shelf development boards and display modules.
- Validate display feasibility before custom PCB miniaturization.
- Build the app MVP around local storage and BLE first.
- Delay custom tooling until fit, battery, and user experience are proven.
Actual costs may be lower with in-house engineering or higher with an agency. Final unit cost depends on quantity, display supply, enclosure, assembly, testing, and compliance.
Prove the hard parts early
| Risk | Why it matters | Mitigation / test |
|---|---|---|
| Color E-Ink fit and refresh | Panel size and refresh behavior may conflict with wearable size and interaction expectations. | Test real modules early; measure refresh, partial updates, ghosting, sunlight readability, and supply availability. |
| Battery life | BLE, haptics, and frequent display updates all consume power. | Measure current in each operating mode; validate standby and daily-use profiles before claiming runtime. |
| Counting accuracy | Missed or duplicate presses undermine trust. | Test debounce, rapid presses, low-battery behavior, restart recovery, and reset protection. |
| Comfort and tactile feel | A device can work technically but feel awkward or distracting. | Test enclosure sizes, skin contact, button force, left/right use, and haptic patterns with real users. |
| Privacy and sync | Session history is personal; reconnects can produce duplicate events. | Local-first storage, clear backup consent, authenticated pairing, sequence-numbered events, and recovery tests. |
| Novelty / patentability | Existing smart counters may already offer some of the proposed features. | Search prior art, document distinctive technical mechanisms, and consult a patent professional before public launch. |
Prototype acceptance checklist
Track validation status with the checklist below. Checking items records your review in this page only; it does not represent a passed engineering test.
Make the first prototype prove one thing
The differentiator is the experience.
Build a wearable that counts flawlessly offline, communicates milestones through a recognizable tactile language, and uses color E-Ink as an elegant, low-distraction interface. Start with a finger-loop form factor, validate the display on a bench, then miniaturize.1. Source
Find 2–3 candidate color E-Ink modules and obtain dimensions, interface details, refresh specs, and quotes.
2. Prototype
Wire up BLE, display, button, and haptic driver; measure actual power and refresh behavior.
3. Validate
Test comfort and interaction with target users before committing to custom tooling or production.
