Jakim API migration #82
Conversation
⬆️ Upgrade package
Notification is disabled temp.
to providers folder
|
Work in progress 🚧
(Updating location database) |
in manual location chooser
Xjadi |
|
Currently changing how location are stored in device. Previously I save the index, egg |
azan type
| DateTime.fromMillisecondsSinceEpoch(dayTime.times![0]); | ||
| DateTime syurukDateTime = | ||
| DateTime.fromMillisecondsSinceEpoch(dayTime[1] * 1000); | ||
| DateTime.fromMillisecondsSinceEpoch(dayTime.times![1]); | ||
| DateTime zuhrDateTime = | ||
| DateTime.fromMillisecondsSinceEpoch(dayTime[2] * 1000); | ||
| DateTime.fromMillisecondsSinceEpoch(dayTime.times![2]); | ||
| DateTime asarDateTime = | ||
| DateTime.fromMillisecondsSinceEpoch(dayTime[3] * 1000); | ||
| DateTime.fromMillisecondsSinceEpoch(dayTime.times![3]); | ||
| DateTime maghribDateTime = | ||
| DateTime.fromMillisecondsSinceEpoch(dayTime[4] * 1000); | ||
| DateTime.fromMillisecondsSinceEpoch(dayTime.times![4]); | ||
| DateTime isyakDateTime = | ||
| DateTime.fromMillisecondsSinceEpoch(dayTime[5] * 1000); | ||
| DateTime.fromMillisecondsSinceEpoch(dayTime.times![5]); |
There was a problem hiding this comment.
X perasan part ni patut la notification salah2 haaaha
|
Alhamdulillah, released update 2.2.2 I'll take more about this whole purpose for API migration here, later. |
Reason behind this migration (to JAKIM API)Perhaps useful to some people or even me myself in the future 😉 Let's start with the problems. For this app, I've been using 2-3 different APIs. There are always things that I like and things I don't. Common weaknesses in third-party APIs (Azanpro, WaktuSolatApp, and mpti906) that I found is that the prayer times is outdated from JAKIM prayer times. JAKIM always makes amendment and correction to their prayer times over time, and most third-party APIs that take some times (a month or more) to process those changes. The precision of prayer times is vital for a Muslim, and it makes me uncomfortable if this MPT app shows the wrong prayer times. The advantages of these third-party APIs (except WaktuSolatApp API) are having good documentation and reference. So, that leaves us with JAKIM API, which we can guarantee is the most reliable source of truth for Malaysia prayer times. Yes, but the problem (or weakness) is their API is not public by default; I never saw the docs to use the API. People found those API by inspecting the network traffic in DevTools. So, there is a risk that JAKIM might change their endpoint without notice, and hence breaking the app (oh, I might just overthink this). I have more to say here, but I don't know how to say hahaha. And sorry but I feel nobody will understand incl. myself in the future hahahaha Oh, did I mention that JAKIM API also most of the time went down? They have excellent reliability on the database but are poor at managing server loads etc. So, in conclusion, I chose JAKIM API because of its data reliability for a long run, inshallah, and to overcome the aforementioned problem, I made a backup API, which is just a 'clone' to the JAKIM API just in case their server went offline, this backup API will be used. Edited 22/2/23:mpt-backup-api is replaced by mpt-server |
Yes, again. For the sake of long-term reliability