🎉🎈🎂🍾🎊🍻💃
Simple Sehri/Iftar timetable consuming a prayer times API
Sehri/iftaar times (when to start and stop fasting) during the month of Ramadan is usually distributed as tables like here and here.
While exhaustive, it can be annoying to track down the proper timee, esp if one is stuck in the subway without internet (for instance).
This app connects to an API built on top of a patched version of this project (I found a bug with scope in the python implementation, my patch has not yet been submitted upstream because I did not see any way to achieve this on the code manual. If anyone knows of a way to achieve this please make an issue!).
The API, also developed by me, is currently deployed to AWS Lambda (and open sourced! Check it out here!). It is available for consumption here. (NOTE: this app still runs on older version of this API, will switch over once the open sourced version reaches feature parity).
This app is an offline-accessible, persistent client for the API mentioned above. It can be added to the homescreen for easy access and also supports ICS downloading functionality.
NOTE: By default times are calculated with the ISNA method.
This app uses the Geolocation API to attempt to calculate lat/lon coordinates of user. It will commit this value to localStorage for subsequent use. Given the lat/long, it connects to the API mentioned above and displays fajr, sunrise and sunset times + prayer times for the day. Additionally, there is support for looking forward and looking back in time.
Using service workers, there is robust support for offline access and viewing. On initial load, the app pulls in content for the next N days, where N = [last day of Ramadan - today]. This data is committed to cache and used by the ICS generator to build events to save into iCal.
To enable offline features, it is required that the app is loaded once over an internet connection. It does take some time to pull in the remaining days of Ramadan calculation but once that is complete it should be fully and equally functional offline and online 👍
- If lat/lon fails, display input for user to pass in city/country (currently only defaults to NYC)
- Support ICS files (DONE) / google events
- Add test coverage
- favicon (someone plz halp?)
- better / more granular ICS support
- build tooling (desperately needed)
- maybe convert into React...?
The implementation of the feedback submission feature requires the use of Webtask and IFTTT. In particular, the Maker Webhooks feature of IFTTT is invoked when user submits feedback. This is hooked into IFTTT to create a new issue on Github as feedback is submitted. In order to satisfy CORS requirements and also protect Maker Webhook API Key, a webtask function is used as proxy - it simply sets the correct CORS headers and also hides the API Key in the Secrets management tool. The function that is currently deployed to webtask lives in the serverless folder and the key is called iftttKey.
Icon for homescreen.