Comments (6)
My suggestion (which is also the easiest way of implementing this) is using the DRF viewsets provided in this package by including them in your urls.py. Via these URL's, you should register devices in the background processes of your app.
If you want to send messages to an installation of an app, you will not connect your FCM django model with a user, otherwise you will.
If you go the unathenticated route, you will register a device upon installation and refresh token when needed. If you connect your FCM django models with users, you will register devices upon logging in and remove tokens upon logging out.
And yes, all the details that firebase needs for its operation should be entered in the firebase console.
from fcm-django.
@xtrinch Thanks a lot for coming back to me on this.
Please do not mind my questions, i am still keeping my baby steps in this process.
My suggestion (which is also the easiest way of implementing this) is using the DRF viewsets provided in this package by including them in your urls.py. Via these URL's, you should register devices in the background processes of your app.
Lets assume i go with DRF.
- so my mobile app should call the below url somehow at the background during the installation process?
mysite.com/devices
or /also - Person visiting the url (mysite.com/devices) through chrome browser will be able to register and be able receive notifications through the firebase notification for web method?
If you go the unathenticated route, you will register a device upon installation and refresh token when needed. If you connect your FCM django models with users, you will register devices upon logging in and remove tokens upon logging out.
My idea was to anyway register the user only once during the first installation only, not every time the user opens the app, so your first statement is what is applicable for me.
Thanks a lot for your time and support
from fcm-django.
Yes, at some point your mobile app should register your device. I would say after the installation is finished, and then ofcourse refresh the token when it expires.
For web notifications you should register your web clients the same way you register your mobile devices. As this is fairly new, I'll be adding 'web' type to FCMDevice token. I'm also preparing an example app how to use it with service workers. You will also be needing HTTPS for that, since service workers do not work on HTTP. There are many tutorials on web, but I'll post a link to my example project when I'm finished, that should be sometime this week.
from fcm-django.
Thank you @xtrinch , i will try my luck with this.
I am planning to build a normal NativeScript mobile app just to check whether i will be able to send the message or not to my mobile.
Thanks for all your support.
from fcm-django.
@just10minutes I'm being very late, but here's the example project I was talking about:
https://github.com/xtrinch/fcm-django-web-demo
from fcm-django.
@xtrinch thank you very much. I will have a look at this.
from fcm-django.
Related Issues (20)
- Setting `content_available: True` HOT 2
- is_cool=True from the docs HOT 1
- user and device type filters in admin dashboard HOT 1
- `InvalidArgumentError` should not cause deactivation of token HOT 8
- Celery and FCM-django HOT 1
- Problem with sending notifications to topic in bulk HOT 7
- Sound and Badge not working when notification arrives in IOS HOT 4
- Documentation about installing with pip seems to be broken on readthedocs HOT 3
- Can this package be compatible with firebase-admin 6? HOT 5
- Add updated_at field HOT 21
- Backward compatible Updates!!!!! HOT 3
- unique registration_id as textfield broken on mysql HOT 11
- USER_MODEL configuration in FCM_DJANGO_SETTINGS not working HOT 5
- Compatibility with Python 3.11 and Django 4.2 HOT 1
- Deprecated send_all() and send_multicast() methods HOT 6
- set badge count dynamically by user HOT 3
- Issue in migration HOT 6
- Changes related to the firebase API migration (batch send) HOT 2
- OperationalError: "max key length is 3072 bytes" when running tests w/ MySQL w/o migrations
- Incorrectly marking devices as inactive HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fcm-django.