Does SignalR work on Mobile - mobile

It might be a simple question but I am struggling to find the asnwer. Can anyone tell me if SignalR is supported across mobile browsers such as S3 or pads etc? I can see it falls back to long polling if websockets are not supported but I can find out if this is supported in mobile browsers? I found an online tic tac toe demo but this doesnt work on my mobile.
Thanks for anyhelp...
M

Do you mean in the browser or if native apps can do it?
If the browser supports the required transport specs, with long polling being the lowest common denominator, then it should work. It's "just" HTTP in the end. I can confirm it works in Android with Chrome for sure.
Same pretty much goes for native apps. If they have HTTP support, they should be able to use SignalR. There are a few implementations of SignalR clients for diff. mobile platforms out there already.

Related

Implement face authentication in React App

I wanted to create a React Application that could be unlocked via Face Authentication similar to Windows Hello. How does face authentication work? How can I make this work? Many android applications and iOS applications already have this functionality. Is there any website implementing such functionality?
The WebAuthn API and FIDO2/CTAP2 spec is supported on all major platforms/browsers now, including iOS, Android and Windows 10 (Hello). This means you can implement a similar experience to native iOS apps in a browser application if you wish as well as supporting FIDO compliant security keys also.
You can try it for yourself here: https://webauthn.io/
You'd need a backend that can support registration of credentials and authentication of assertions however. This is potentially non-trivial depending on what you have in play but library support is improving all the time.

How to Ensure Installation of Mobile Web App on Device Only?

I'm working on an AngularJS mobile web app and am getting ready to deploy to Firebase Hosting. Does anyone know how to ensure that only devices can install the web app and prevent desktop browsers from viewing? I'm trying to protect the client's intellectual property as well as my own by making a reasonable attempt to disallow the source code from being read. Thank you!!
It's not possible to prevent the reverse engineering of any web application.
Developing a mobile application using native code may make you feel more secure about the intellectual property, however once a would be attacker gets the software on to their own hardware they will have the opportunity to defeat your software.
I wound up using ng-device-detector to determine whether the user was using a mobile device or not, and delivering a different template page depending. This library contains an isMobile() function that works great.

Mobile Chat Backend Play Framework vs Netty

I want to develop mobile chat backend for android and ios clients. I have experience in playframework 2 with java. Do I need to learn and use netty framework for chat backend? Playframework is also a nio framework running on netty. I can not decide which one to choose? Will be playframework enough for high traffic mobile chat backend?
The Play framework should be enough. No need to touch the bare metal (Netty) unless your doing something very complicated (special protocols, etc.). For your use case, you probably just need to familiarize yourself with the WebSocket Protocol and specifically how to set them up in play.
Your next step would be to setup the clients for android and ios. For android you could take a look at Java-Websockets and while im not familiar with iOS, a google search returned this which might be somewhere to start.
All that being said if you'd like to avoid the extra fluff that play provides (sessions, cookies, templates, routing, asset managment, Akka, etc.) and you dont think you will ever need them, then definitely go with Netty if time to learn is a non-issue. Note that with Netty the client libraries above would still apply if you use the same Websocket protocol.

Lightweight HTTP streaming solution needed?

I'm developing a web based backend to an embedded system to which we have implemented the code for the servers get requests (all built in c). I need a lightweight solution to stream an array of data values to populate a graph built using the canvas tag. Im looking at the comet pattern and potentially the iframe solution.
However Im not sure how to implement this with out a full web server running? Im fairly new to web technologies and any help or pointing me in a direction would be much appreciated!
Thanks
Matt
As #Joe suggested in a comment, have a look at web sockets. Here's a few useful links to get you started.
Websockets 101
socket.io, client and server implementation
libwebsockets – HTML5 Websocket server library in C
Websocket test suite

How do Mobile Apps communicate with a server?

How do Mobile Apps communicate with a server? Does this communication happen over HTTP or are there other methods (for instance, I guess a mobile app could open a socket)? Does this differ form device to device? Is there one most commonly used approach? If the communication happens over HTTP how do the URLs look like? Is there a way to identify the app based on the the "User Agent" in the HTTP request if the communication is happening over HTTP?
Mobile Apps can communicate with a server in many ways. Mobile apps can also use other features of the mobile. For instance SMS , MMS. Its pretty open really. Your question could be "how do computers communicate with a server?".
A mobile app can be a simple as loading a web page. This would be http.
The problem with mobile apps. They run on phones. There are lots of different phone manufacturers and its up to them (in some case the mobile phone operators also have weight) what to allow the programmer to do by the choice of operating system.
If you are getting started with mobile apps. Take a look at android its pretty simple to get going with if you know a little about programming.
As for the useragent. It depends but usually if you are using the http api on the phone, you can set the user agent to what ever you want it to be, its just a string.
Hope this helps!
Communication usually happens over http. Applications usually identify themselves in the User Agent field

Resources