I searched and found a lot of confusing answers to what exactly a mobile station is. The answers range from a simple mobile device to a PABX. Could somebody clarify this for me?
I Found your answer on this GSM module article.
A mobile phone and Subscriber Identity Module (SIM) together form a mobile station. It is the user equipment that communicates with the mobile network. A mobile phone comprises of Mobile Termination, Terminal Equipment and Terminal Adapter.
Related
I understand that different layouts can be designed for Mobile Phones and Desktop Websites. But is it possible to implement two different approach implementations for Mobile Phones and Desktop.
For instance, is it possible to have one page designed as drag and drop for websites
and the same can be designed as,
select stepwise for mobile phones.
Any clue or library or implementational approaches will be greatly appreciated. At the last, i am trying to implement the same website page in ReactJs.
You can have Platform specific code with different file extensions as follows
dragndrop.native.js//mobile platform
dragndrop.js//web platform
More info here Platform React-Native Docs
I've to share a mobile screen and display it on a browser using WebRTC. I then have to take control of the mobile screen.
I've researched this and know I can share a screen browser to browser using chrome(with extension) or firefox(after certain flags are set). Some information I've read suggests that screen sharing on mobile is not possible and then another article said it was but I think they meant be sharing through the chrome browser on a mobile.
Some of the the information and posts I read are dating back to 2013/2015/2016 and I wondered if there is any new information on this?
Is screen sharing on mobile devices(android or iOS) possible using webrtc now?
is screen control on mobile devices possible?
Thanks Andrea
I also investigated this topic a few days ago and it seems to me we are on the verge of the next step and the technology hasn't totally settled yet. Screencapture is mostly working with (very) up-to-date browsers and (still) an extension or some kind of white-listing. I could not find any kind of hint that a "remote control" mechanisms are part of webrtc and the getUserMedia implementations. Unfortunately.
ICE seems to work fine for most scenarios (if you don't mind waiting a minute) and Tickled ICE adresses the problem in an interesting way.
Mobile is very confusing indeed as the market is even more heterogeneous.
Maybe we should open a wiki or a chat channel or whatnot they habe nowadays on stackoverflow :-) I think I will have to read about this "community wiki" checkbox down there...
The most promising thing I could find was
https://inthelocus.com/
Still trying it out in different scenarios.
[This might not be an answer...] I was on the same topic and then I noticed there's an existing tool (SDK) to serve the similar purpose: https://cobrowse.io. It works good in both the demo video and the simulator web page. Yet I'm not sure if it utilises WebRTC...
I am trying to create a mobile P2P game with network library written in c (enet/libuv).
I have read in some forum that there is risk of blocked port by the router and I need to do something called port-forwarding.
Most of the topic related are for console games and I'm trying to do mobile game, which theoretically should be the same.
Sorry for my noob question but, will it be a big issue for my game and how can I fix this problem (without using any third-party help) ?
Many thanks for the help.
I have a business application which I am going to extend by creating mobile versions of it for the Blackberry and iPhone lines. One of the requirements is for the mobile devices to be able to display reports.
What is the easiest way to do this? Output the report as HTML or something else. Does this also require a crazy amount of scrolling on the device to view things?
in my opinion you had to think the mobile web differente from web. The operation available from mobile must be the operation the user need to do now, he cannot wait for them. Generally viewing a report can be postpone to be done from Desktop pc.
So suppling a mobile version of a web application involve also the choice of which operation supply and wich don't.
With the advent of smart phones, individuals are now able to access a given site or application in one of three ways:
Through the same site that is rendered on desktop machines
Through a minimized mobile version of the site
Through a proprietary mobile application
In an ideal world, users could choose from any of those three methods. However, there is a cost associated with implementing additional interfaces on top of the existing Web interface.
I'm seeking verifiable information (statistics, trends, Gartner predictions, etc.) that could help someone justify the creation of a minimized mobile site and/or proprietary mobile applications vs. having a well-crafted site that renders fine in mobile browsers.
I found an article covering Nielsen's 2009 recommendation but the article seems to suggest that you should address mobile users, not so much how to determine which method(s) are more appropriate (not to mention there aren't any references to mobile apps).
If your site renders fine in mobile browsers, why would you need a minimized one? Remember not everyone has an iPhone. Blackberry users usually need a special version, unless your site has Wikipedia like simplicity.
You can look at your logs and see how many users come that have mobile phones. Check this against the bounce rate, this will tell you if they can view your site or not.