I am Developing an App which needs to Call (Audio/Video) to Users, Add them in ongoing Call like whatsapp does and one more functionality that the users can join a call.
I got to know that for joining Quickblox Conferencing should be used.
But I am unable to get any callback for any conference started.
Does Conference feature act as a call also??
QuickBlox offers 2 ways of implmenting multi-party calls:
Peer-2-peer calls, allowing up to 4 participants at once. This feature is available with all plans including the free one.
Conference calls using SFU technology, allowing up to 12 participants at once. This is feature is available on the Enterprise plan but it is possible to request a demo.
Apart from native OS support, QuickBlox also has React Native SDK and Flutter SDK.
Related
We are developing an app for Android and IOS for students. student can receive notification for upcoming events like exams or interviews.
We are between two decisions: Using FCM with the development of a backed which manages the sending of notifications and the registration of tokens or using the schedulers that exist in IOS and Android then download a list of events from an API regularly and trigger a local notification which will require less development on the backend side but a little more on the frontend side.
What would be best in your opinion and can we trigger a notification even if the app is closed for the 2nd solution?
I would deffinitely recommend to use FCM. It is much easier than it looks like and the performance of your notifications would be much better regarding stability, timing, battery persistance and other. You can use on of the Firebase databases to store the notification tokens and the Firebase Cloud Functions to send them from there. I have made a very similar App for Kindergarden children and it works great. I'm not sure if it would even work at all when you do it on your own. At least not as you expect it. For me that sounds like much more work.
I am trying to build an application which works this way: I as a user want to start a call with another user. The way I want the connection be made is by random. So it will connect to one of the many clients out there by random. Also when other clients try to make a call, it should connect to another random client and so on. I want those phone calls be made via application(such as WhatsApp) not as a phone call.
Now, the question is; is Twilio a good approach for this purpose?
If yes can you tell me which of their feature would fit my app the best?
Thanks for any suggestions!
Twilio developer evangelist here.
I can answer that Twilio would be a good approach for you to do this within your own application. I'd recommend using Twilio Video to build this as it allows cross platform communication via audio or video (in your case, you may not need the video, but this will give you the best audio quality).
As an example, my colleague Dominik built a video roulette application. It is the case that the interface was built in JavaScript for the web, but the idea would be the same for a native app. The code for the server side part of the application should give some insight into how to connect random pairings.
It's also possible to integrate Twilio Video with CallKit and Connection Services so that you can make outbound calls to other devices that ring like a real incoming call.
Is there any way currently to do a parallel payment in paypal with the rest api? I am building a mobile application and can only use the rest api system however there is no documentation on how you can use parallel payments with REST.
You can do everything else so it seems to me like the developers got to that feature and just gave up :P.
This feature is a huge part of our website and if we cannot use it on the mobile app it will mean we have to redo how we handle transactions on the site so that both areas are consistent.
If this feature is not available since rest was supposed to be the refresh of all their API's to support newer tech is it coming? Does anyone know and if you do any information on a timeline would be helpful.
REST API does not support parallel payments at this time, it's in the product road map but not yet in the released APIs.
An alternative for your use case is to integrate the webview embedded Express Checkout flow into your APP, it provides the most identical experience to payers since the new UI was released.
Is there a way to send push notification with passbook on android ?
I found this https://www.pass2u.net, but i'm not quite convinced...
pass2u have an open API and offer free access to pass issuers with less than 1000 updates per month. One advantage over PassWallet is that their revenue model is not dependent upon advertising.
Both pass2u and PassWallet have reliable APIs that closely mirror the Passbook webservice and can be easily implemented with minimal overhead.
One further advantage of Pass2u over PassWallet is their support for Baidu push. If you have users in China then PassWallet updates will not work because they are dependent on the Google cloud messaging APIs which are not available.
The PassWallet app supports push notifications. It uses the same mechanism and API as Passbook/Wallet on iOS, the only difference being where you send the push notifications.
When a pass is installed, it registered with your service as normal, but in addition to the serial number etc. a URL is provided too. You then send a message to that URL.
You'll find more info here http://attidomobile.com/portfolio/passwallet/
I am working on an enterprise app which allows users to perform CRUD operations on data
under their profiles, sync it with a backend, share it with other users and view it across multiple platforms.
The app works on 3 platforms
a) as a webapp in browser
b) as a native iOS app on iPad
c) as a native android app on android tablets
Now we want to give the app for free for a trial period of 3 months after which we want to
charge our users a monthly subscription fee if they want to continue syncing their data
with backend. If not, they can use the app as a native app which doesn't have a backend
and they won't be able to share their data across platforms and with other users but will
be able to use the app as a native app with no backend.
For the monthly subscription fee, we wanted to integrate Paypal payments into our ipad
app.
There are 2 gray areas which is causing us confusion
a) Apple might reject the app due to paypal integration as it favours in-app purchases/itunes.
b) Apple states that users can be charged only for "real world service". Does our kind of service qualify?
We prefer getting some definitive information rather than implementing paypal payments and
getting rejected by apple which will set us back by 14 days. Any help would be much appreciated.
I don't think you'll get "definite" information here, since stackoverflow does not have internal information on Apple's strategies. You have to try and find out. I know Apps with monthly subscriptions that use in-app purchases (like Trillian).
If you want to make sure it won't get rejected, exclude the payment process from the app. You are using accounts and some accounts get paid "premium" functionality. Just let the users pay through your website or redirect them to your website if they want to buy from iPad. My guess would be that Apple will otherwise want you to use in-app purchases for the subscription.
About the "real world service", that should be no problem.