Using Parse and QuickBlox together - ios

Im very new to the backend. Im making a plan to build an iOS Social App that uses Parse for the backend. But since Parse hasn't supported real-time chat feature so I have an idea that uses the Quickblox chat API to build my real-time chat feature. Im not sure whether it is possible or not so I ask here.
Honestly I haven't try anything because I just make my plan. It must be clear before I start so I will build my app faster.

Yes, It's possible.
QuickBlox user model has external_user_id field, you can connect Parse user and QB through this parameter. Or vise-a-versa.
Next, for example, you use Parse user. And you would like to start chat with other Parse user.
You should:
Get QuickBlox user by Parse user.
Login to QuickBlox chat
Send message.
http://quickblox.com/developers/SimpleSample-users-ios#Integrate_QuickBlox_with_your_existing_User_Base
Also, QuickBlox has the same features wich has Parse. I recommend you to review your requirements and maybe you no need to use Parse because in any cases use 2 platforms it will be a bit complicated to support.

Related

Creating a push notification system with a React Native front end and a Java Spring back end?

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

incorporate user messaging using firebase and swift

So I am trying to find a way to incorporate a messaging feature within an app. I cannot find any up to date information on the web, so I figured I'll ask on this platform. Can someone guide me in the right direction?
I am currently using firebase and swift as building tool for my app. I am looking to build a simple chat/messaging function where users can message each other like instagram, facebook and airbnb allows users to do.
Firebase provides realtime database for chatting feature and many other features where you need data updates in realtime.
You can refer to https://firebase.google.com/docs/database/ios/lists-of-data where it shows you can handle child-added, child-changed event for realtime updates.
You will have to design your database to incorporate chats in it though and then write business logics to handle it through firebase realtime apis.

Online Data Storage and Transfer with Swift

I am trying to make a series of applications which require the user to make an account and login, therefore they could use the application on multiple devices and have the same data (e.g.. amount of virtual money and player score is about it), however, I have no idea how to go about this, I have decided it would be best for my app not use the apple GameKit (game centre) as it has a lot of limitations (e.g not showing usernames). What methods could I use to do this? Do I need to learn another language
Thank you
You can try Firebase, which serves as a backend especially for mobile applications. Basically, send a kind of a POST request to Firebase when the values you want to store have been changed in your game and send a kind of a GET request to fetch the said values to your mobile app(s). By this way, you can store data on Firebase and fetch it via multiple devices when the same user logs in from different devices.
For more information and a quick start, check this link: https://www.firebase.com/docs/ios/quickstart.html

How can I get Alexa working on my iOS app?

I have been checking out the Alexa Skills kit the past few days. I have also been poring through the documentations for both the Skills kit and the Voice Service. I am just having a little hiccup trying to understand the flow. I have implemented one of amazon's sample skills (favourite colour sample) in the developer console and also wrote a sample lambda function to handle the type of response that will be delivered. Its working on the test simulator and what left is basically getting lambda running through my ios app. However I have the impression that I don't have to use the voice service. Am I wrong? I am quite confused, it would be awesome if anybody who has some more clarity could shed some light on the matter. If I get lambda working also, I think it will accept requests that are in a particular format. Where do I have to send the encoded audio to get a json response to send to the skills kit? To the Alexa Voice Service?
Also I am authenticating my app using cognito and dynamo db. If I were to use Alexa Voice Service, then it is mentioned that the user will have to also login to amazon. So do I still have to work with the login with amazon sdk? Or is there a workaround?
Based on Amazon documentation there are two ways to interact with Alexa:
Sounds like you want to implement the app thru the Companion method.
As far as the JSON goes, i am currently resolving that issue now, (will post answer once I have it resolved).
Basically you have to use AVFoundation to capture audio from iPhone and send 2 https messages to Alexa (One message with JSON Body & the second message with audio captured as body.) Bases on Documentation
Companion App
(You have a device (such as a smart speaker) that you want to add Alexa to. So, you build in support for AVS. Great! Now you need a way to authorize it and associate it with the user's account. This is the "companion app" approach. The companion app connects to your smart product and allows the user to login and authorize the speaker to use Alexa and connect to their Amazon account.)
Mobile OR Website
AVS App
(You don't have a device you need to authorize - instead you want to speak to Alexa from within your Android/Iphone application.)
Android or Iphone
You can find a swift example on github on how to implement a iOS AVS client
https://github.com/chintan1891/iOS-Alexa

Parse.com Javascript SDK for app API or just plain iOS SDK?

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.

Resources