I'm currently developing an iOS app with a custom Django REST backend. Using REST calls I can create/login users and make blog entries. I wanted to implement a chat feature so that my users could send private real time messages to each other.
I have no experience with web sockets and how they work. I wanted to know what is the best way to go about developing the chat feature.
Current set-up:
- iOS app using swift 3
- Django 1.10 for server
Related
Currently building a mobile application that ideally would have functionality that allows one user to "nudge" another user, pretty much the equivalent to a Facebook "poke." For the sake of building quickly, we'd like to use as many third-party libraries/services as possible. So far we were looking into using pusher and expo, but to be totally honest, we are a bit confused as to how to architecture this.
From what I understand, the front-end (ios app) would subscribe (open a socket) to a specific channel/server and the server would then send messages to the client(s) that subscribed whenever necessary. How this works with users being subscribed to every other user they are friends with, I don't understand. What's the proper way to architecture this?
I also read that on the front end, when a user doesn't have the ios application open you can't have any websockets open to the server, so how does that work?
Additionally, how does one bundle notifications??
Really confused with this, any help would be greatly appreciated.
Chris
Well, push notifications now mostly are implemented with Firebase. This is a service inside most of mobiles, so you only need use these libraries to implement your client application.
From the server, you only need to consume a rest api of Firebase.
Now there are permissions to allow mobile applications receive push notifications in background. You do not need to implement a socket or websocket, that is a feature of Firebase.
Read more about this.
https://medium.com/google-cloud/push-notification-for-react-native-bef05ea4d1d0
https://dzone.com/articles/how-to-add-push-notifications-on-firebase-cloud-me
I'm trying to build a live updating dashboard in rails 5 with a actioncable. I was searching for some example which might guide me into implementing this but all i found was some chatting apps. I'm planning to use Google Charts. How would i be create an polling Channel which will an API will get data from server and display in my app. Because chat app are calling when user send a message. I want to make it automate polling every X seconds. Any links or reference will be quite helpful. Thanks!!!
I developed a web application for a customer.
Web users can login and have their private account.
The application manager want to send "push" notification to users connected on iOS mobile devices.
Since I cannot achieve this feature with a simple web applications but I don't have resources to develop a native iOs application, the question is:
Is there a simple way to create an iOS "wrapper" to my web application and enable push notification for that app?
It will just be a webView pointing to my web application?
I'll be grateful if somebody can point me to resources, skeleton apps, alternative solutions, etc.
The kind of app you are talking about would be rejected from the app store due to the poor value aported in comparison to your website. This is part of the policy apple applies for a while now.
I've only recently started to delve into how building apps work. I'd like to know what the general setup is for a mobile app and a website, in which users can update information on the app through the website.
I'm trying to learn how to make an iOS app with Swift, and use Amazon Web Services as the backend for it. If I wanted to then make a website that would change data on the mobile app, would I have to create a website from scratch with Ruby or Python, and then somehow connect that to the same AWS backend that my iOS app uses?
Thanks.
Usually, most data is stored on a website. Your website can have ways of viewing the data, such as web apps, like jcaron said. An app is usually used for viewing data from the website. When I develop apps (with Swift) I setup a database on a website and connect it to the app using PHP scripts. Then I make the app, with it's own UI, which does HTTP requests to the website and uses the data.
That's a very broad question, with lots of possible answers, but here are some of the options:
you have a native (Objective-C or Swift) iOS app, with its own UI, etc. It exchanges data with your back-end server, which stores stuff in a database and/or forwards messages between clients. Then, you have a website, using any language/framework you want, accessing the same database.
you have a web-based application: you use exactly the same code (with responsive design of course), serve it from your servers using any language/framework you want, and just embed that in a web view in your app
you have an hybrid application: this is close to the previous option, but you do most of the coding client-side (i.e. using Javascript, possibly with frameworks such as Angular) within a Cordova/Phonegap app. The same app would then be deployable as a native app as well as served as a website. You would just have back-end code on the server.
I'm trying to figure out the best way to develop API for my iPhone and Android app with Parse.
Parse has separate iOS and Android SDKs that can create and modify objects. It's good choice, but then I'll have to send push notifications and it's obligatory to use Javascript Cloud for this case (as far as I understand).
So I'm thinking about using just Javascript Cloud as a wrapper and doing all things with data on Parse side (without using iOS or Android SDKs).
Does it seem like a good choice or I should dive deeper into native SDKs to eliminate server-side even if it's hosted on Parse?
I don't think that it's obligatory to use Javascript Cloud to send push notification. In iOS case:
https://parse.com/tutorials/ios-push-notifications
As you can see, you have 4 choices for sending push notifications:
Parse website, REST API, inside the app itself and also from Cloud code.