django-push-notifications VS django-todo-api

I used django-push-notifications because fcm-django was a pain in the ass for reasons I don't particularly remember (I just wanted to build a proof-of-concept).

I used django-push-notifications as a library. You'd want the django-push-notifications[APNS]==3.0.0 for iOS I believe.

- I did research into the best library to use. django-push-notifications (https://github.com/jazzband/django-push-notifications) looked like the most up-to-date library to use. The APNS portion is built on apns2 (https://github.com/Pr0Ger/PyAPNs2)

Hey there, I've been looking into realtime communication between a Django backend server running on Django REST Framework, and a Flutter application. I've researched into Django Channels (Websockets), and the "Django Push Notifications" package (https://github.com/jazzband/django-push-notifications). I'm sure FCM/GCM will be a piece of cake to handle, but what about Android devices which do not support the Firebase SDK? E.g. Huawei, Mi devices etc which do not have Google Play services on them.

If you want to see a naive implementation, you can check out a basic version I made here (the good stuff is in serializers.py and views.py).

Make sure you're in the same "session context", ie. same domain name, same port, same subdomain (you may need to use a reverse proxy like nginx to direct the requests so that they appear to be in the same session context) (Example nginx.conf here). Also you may need HTTPS for all this to work so check out mkcert if you want to use HTTPS (self-signed certificates) on your local network.