I'm looking to create a mobile app that controls lights that are connected to a Google Home, is this possible? I'm basically looking for a Google Home equivalent to Apple's HomeKit framework.
This is a similar question, but also three years old, so I'm wondering if anything has changed, or changing soon with Matter.
The platform does not give programmatic access to developers to the devices in their home. In this regard nothing has changed up to this point. I cannot speculate what may happen in the future.
Related
I've created a basic web-app which guides user to decide first programming language. I've created my project checking through Google Dev Tools iPhone6 view since I'm using iPhone6 also but in real iPhones appearance is not even look close. Is this annoyance only for me or for everyone also? or is there better way to design a web app for mobile? You should check difference from here https://ibb.co/Gcsjsvn and check my repo from https://github.com/kgokdemir/firstlang
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'm a little new to this topic, i've always used to work with responsive design to do this but for a new situation i have to change the content that will load on Mobile Devices than regular PCs, My Control Panel is Direct Admin on Windows server, what i should i do?
check out this answer on how to redirect mobile users to a different site - Redirect mobile devices to alternate version of my site
In addition to this I'll also chime in with the fact that people will browser most sites on both the mobile and the desktop, starting the journey on one and finishing it on another. They might also find something useful on one which they share online, only for another device type to be used when trying to read the content.
These are all reasons why we argue for content parity.... the same content for every instance. I'm sure your client believes they have a good reason for this, but I would encourage them to re-evaluate the decision before starting this process.
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.
I am developing a mobile site for iphone, and i want it to be used in other mobiles, for example, gphone, blackberry, sumsong, motorola etc.
what should i do for adapting the mobile site for so many different mobile devices?
Thanks for any advice.
Unfortunately I do not think there is an easy answer to this, other than to say that the simpler you make your mobile site the more likely it is to appear correctly/consistently across multiple devices/networks. You also need to consider the 'app' mindset with iPhone, where something that previously might have been presented simply as a web site, is now frequently presented in an app instead. Finally, bear in mind that many phones do not support flash (iPhone famously..), silverlight, javascript etc. If your site loses too much of its look and feel without these than you may have to redirect to targeted sub-sites per phone type.
See this similar question which may help you get a feel first for how your web site looks on different devices and in different networks:
Testing Mobile Sites
If you do need to change the look and feel for different phones, then you will need some way to detect the phone types - there are many articles etc about this which you should be able to find with Google - for example:
http://www.hand-interactive.com/resources/detect-mobile-php.htm
Again, it would be good to test whatever one you use in your target network to check it works as expected (operators may use devices, for example proxies and optimisers, which may affect how things arrive at your webserver or phone...).