Websocket is for browsers only

I am trying to program my own Objective-C and Native Android application using 3rd party libraries. I have already selected libraries and I am already progressing in it.

One person on my team claims that the website is currently implemented in concentration in web browsers. If we use these third party libraries to implement them from our own application, it might be unstable.

He says that maintaining a web layout connection from a native mobile app can be trivial, but webkit browsers already do this naturally, so we should consider building a hybrod app.

Can anyone comment on this?

+3


source to share


1 answer


Websockets can be used by any client (read: "application") as long as the client implements the Websocket protocol - no browser required (or hybrid).

For example, SocketRocket is an Objective C library that helps you build Web sites in native iOS apps.

Here's a good article here on implementing websockets in iOS and Android apps.



I think implementing Websockets without Webkit is the best way. Hybrid app creation can impact performance. If you are only using one function (websockets), Webkit might be too heavy.

The only question is, are the libraries you are implementing mature enough?

Good luck!

+1


source







All Articles