I am trying to communicate between Android and iOS app using Ejabberd Server setup at backend.
For Android I am registered with "Conversation" app.
For iOS I am registered with "ChatSecure" app.
I am able to send image if both users are available on same app. But If one user is logged in with Android and another with iOS then image transfer not working. It gives error due to "OMEMO" encryption.
Any idea how I can remove this encryption?
Could you say what is the difference between "Conversation" app and "ChatSecure" app ?
Related
I'm currently developing a programme that will need app developers to listen out for a (ideally) silent notification from my Django server. Right now, I'm testing with a React Native app I've made but I don't know how to implement something like this. Basically, when something happens in relation to a certain app on the server end of things, I want to send a notification to that client app to react accordingly. Almost like a webhook but for mobile.
It's important to know that in practice, I won't be the owner and developer of both the client-side app and the server-side software, just the server-side. If anyone knows how to do it natively on either Android or iOS that would be appreciated too.
I am working on a deep learning android app. I have trained and tested the model and everything is complete in that area. Now I have to deploy it on the cloud.
If a user used the app their data is sent to the model which resides on the cloud and the result are sent back to the user's mobile app and displayed. The reason the model is deployed on the cloud is because it is to be an "online learning system".
What I don't understand now is how do I connect the android app user interface (developed in android studio) and the model.
Should I use Kafka or anything like that? If yes, what steps do I need to follow to deploy my jupyter notebook to the cloud and then connect the whole system to the android app user interface.
You wouldn't use Jupyter. You'd embed your model in a web server and interact with it like any other HTTP service from your mobile app
Kafka alone isn't an HTTP service and doesn't host ML models; it would need to be paired with other tooling. KSQL, for example, does have a REST endpoint. Example - https://github.com/kaiwaehner/ksql-machine-learning-udf
Currently I am working on one android app which takes user's info and let them register for the app.
But I am having problem while connecting my backend with my app.
In order to save the data I use server host which I don't know how to implement for android users.
Help me with this so that I can start building my apps..
If you are sending basic user info, maybe you can publish a rest webservice on the server and consume it from android app. im using retrofit right now to consume rest webservices from android and is very easy to use.
How can one find out which or what an app is using as a back-end server?
Assume you are making an app and you are using Parse.com as your back-end server. You made an app and go published it to the appstore. Later, what are the odds for some one else to find out what did you use as a back-end server? Can she/he find out that you used Parse.com ?
What are the odds for an iOS app and Android playmarket app ?
Simply see what networks calls are being made by the app. No need to decompile or anything like that. Simply log network calls on your home network. Your Wifi router might do this or you could setup a proxy server that logs all requests.
I am new to both Android and Rails. I built a simple Rails app to log in to post comments and leave replies to others' comments as well. I am trying to see how to build a native Android app to respond to this Rails app and have come across a question with sessions/cookie.
In order for me to build a native android app that can allow a user to log in and browse through the rails app, do I have to write a code that receives cookie from the rails app and store it in android sqlite database? Thanks
Are you trying to load a view in HTML (an embedded browser), or render a view on the device using the native controls? If you're doing the former, surely Android already handles all this for you, just like a WebView in an iPhone app does?
If you're doing the latter, you should build an API that uses something like OAuth for authentication, rather than maintaining a session cookie. This approach means that you store a pair of (revokable) OAuth credentials on the device and that you don't need to work with the user's username/password.
I'm not sure on what your end goal is here.