You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usecase: When memorizing long surahs, after memorzing page by page, I try to revise hizb by hizb. It will be helpful if I can play the audio for a hizb easily.
Current workaround:
I open the page where the hizb begins
Tap "Play" (at bottom left corner)
If hizb begins in the middle of the page, press and hold the first ayah and then tap "Play" in the context menu
Tap "Modify"
Tap "To"
Scroll to the ending ayah of the hizb (which I should have noted down already)
Tap that ayah.
Tap "Play" (at top right corner)
Proposed solutions:
In the below "Juz" view where a list of hizb rows are displayed, we can add one of the following two options.
Add a play button above the page number for each row. Single tap to play the full hizb.
Add a play button inside a context menu, which appears when I tap and hold a hizb row.
I would like to contribute to the code if you can give me some pointers about where to work for this feature.
The text was updated successfully, but these errors were encountered:
I believe I understand the issue, but I’m not sure the proposed solutions align with the approach we would take. So far, audio playback has been handled within the Quran UI rather than the main navigation views, and I don’t think I would expose it externally without a proper framework.
That said, I think adding an option to play until the end of a Hizb, similar to what we have for Page, Surah, and Juz', should be fine in my opinion.
Usecase: When memorizing long surahs, after memorzing page by page, I try to revise hizb by hizb. It will be helpful if I can play the audio for a hizb easily.
Current workaround:
Proposed solutions:
In the below "Juz" view where a list of hizb rows are displayed, we can add one of the following two options.
I would like to contribute to the code if you can give me some pointers about where to work for this feature.
The text was updated successfully, but these errors were encountered: