This question can be asked a couple of different ways, but so far it does not seem obvious how or whether it will be possible to specify a single app that a Chromecast device should be locked to - or put another way, can you whitelist the app (not whitelisting the app ID for development) that the Chromecast will run ?
I want to have my chromecast only run 1 specific predefined app, being driven from a (potentially whitelisted host) single host - does anyone know how to do that yet ?
Has or will Google give any guidance on whether this would be a supported use-case (only allow X app on Y host to take over this Chromecast) ?
If you mean controlling the list of "whitelisted" apps yourself, no, it is not a supported use case. Why would you need such feature?
Related
I have a very general question on how to implement VoIP for our current mobile & Web App. (we have an Android+iOS App and a Web Application based on AngularJS/NodeJS).
What we want to achieve
In the first step we want to achieve inter Application Voice and Video Calls. Later on we might expand into outbound calls into the normal telephone network. But this post is mainly for getting info on how to implement only our first step.
general thoughts
We had some experiences with Asterisk before which turned out to be far from easy. So for this project we wanted to get some feedback before actually implementing anything.
thoughts on technology
At first I thought it might be a good idea to use WebRTC, but since it's only supported on Chrome, FF and Opera for the moment and pretty much is unsupported for native mobile Apps we think that WebRTC is probably out of the picture for now. (or do you think otherwise?)
After searching the web a bit more we found this: http://www.webrtc.org/native-code
Has anyone experience with this libs? It seems to us, that this could be the best solution for a modern voip solution (and also would allow us to skip the asterisk server)
The second idea would be to setup an Asterisk Server for ourselves. Every time a user logs into the App we would connect him as a SIP Client to the asterisk. If one user calls the other one we think we should be able to make the call for example with the node package Asterisk Manager API (https://github.com/pipobscure/NodeJS-AsteriskManager).
The third idea would be to use a SIP Provider, but at the moment I'm not sure if that's really the best idea.
Since we're no VoIP experts, are there any other possibilities for VoIP integration into our apps?
Any thoughts on that subject would be very appreciated! Thank you!
The main factor is the network configuration that you app will be working with. Given you're using mobile clients and web apps it's almost certain that you're using the internet and also likely that you'll have 3G and 4G mobile networks in the mix (3G/4G cause a lot more problems for VoIP than WiFi).
Given the above assumption holds the biggest challenge your app will have is establishing media (audio and/or video) connections between mobile clients which are behind different NATs and in a lot of cases multiple NATs. There is almost no chance you'd be able to get by without a server here. The server will be needed to act as a relay point for the media streams for the mobile clients. You will use the RTP protocol for the media and working out how to get it reliably from client A to client B is your biggest obstacle. The signalling side - whether it be SIP, web sockets or something else - will be secondary (note both SIP and WebRTC use RTP to carry the media).
If I were in your shoes the steps I'd take would be:
Install and try out some softphones (blink, bria, zoiper et al) on your own mobile devices, find a SIP provider that supports video calls and get some experience with calls. It may not be the experience you anticipated...
Once you are comfortable with the softphone experience you would then need to make two decisions:
Whether to deploy your own server or use an existing provider,
Whether to write your own client, find an existing one or something in between.
I can answer the deploy your own server question. You don't want to do that unless the VoIP part of your app is going to be something you charge for and make a good margin off. Running a VoIP server and all the security and network considerations that go along with it is a full time job. It may start out being easy but once a few customers start connecting and the fraudsters come along it will take on a life of its own. In the decade I've been messing around with SIP I'd estimate 75% of providers have gone out of business and it was their full time job.
Besides all that I'd be surprised if there wasn't a SIP provider that suited your needs. These days there are highly sophisticated services available that led you control every aspect of your call flow with your own code (anveo, tropo, twilio) right down to free services (sip2sip, sipbroker) that may be all you need to get started.
For the client software there are various SIP SDK's you'll be able to leverage (pjsip).
We are creating our first google glass app and I had some security questions that came up that I can't seem to find a definitive answer to on the web. They are as follows:
What apps are available for us to be able to wipe the glass (factory reset) remotely if they are ever misplaced or lost?
Is there an app or a way to automatically wipe the glass maybe at a certain time everyday of the data that is one them?
When we do a factory reset, is the data securely wiped from the device? Or like a PC is the data still there for possible usage if the device memory is hacked into directly?
If we pass data over the network, is it passed using some sort of encryption currently? Or do we have to take this into account when developing our app?
Is there a way to allow multiple people to use the device without having to wipe the device and setup with another account? The only way we were able to login using 2 different accounts was for the first person to factory reset it and allow the next person to login using their account. What we were envisioning was a way for the device to securely authenticate and allow multiple users to use it differently somehow without having to reset it.
The only current way to lock the device that I found is to create the swipe/tap pattern that is included. Are there any apps that allow for a more secure type of login?
If anyone can help on any of the questions, that would help out a lot.
Thanks!
The MyGlass webapp and mobile app allow you to do a remote device reset. From the mobile app, you can go to Settings while the webapp does it from the MyGlass -> Device Info page.
There is no way to do an automatic reset every day that I'm aware of. What are you trying to do here? Just reset it to a known state every day for development?
At this time, you probably can't count on it being a secure reset.
This is a pretty vague question. Google hasn't provided details on the sharing protocol, but it is a safe bet that this is done using SSL on some level. From their servers to yours using the Mirror API must be done using HTTPS. Of course, if you're doing the network data passing yourself, then it's up to you.
No, this isn't possible at this time. Glass is a very personal device. More so than phones, and most phones don't have a profile feature!
I'm not aware of any, but I'm not sure how much more secure you can get and still be usable. Can you elaborate on what you're envisioning?
Currently my web tools front end is running in OFBiz and is accessible from the whole wide world (www) just like the ecommerce store.
I don’t like that a bit. Although it is protected by strong password.
Can I restrict that app access to certain IP addresses or from local host only?
It would be best if that application can run on different port altogether or listening on 127.0.0.1 interface only. Or both :)
Any experience with this, please?
Kind Regards,
Boris
I'm new to Ofbiz and working within (mostly) the opentaps context. From what I see I'm not sure you can achieve this but perhaps it's possible to change the mount-point of the webapp for added security such that it's not obviously accesible through the default OOTB name.
I'll reply later on in the future when I have looked into this myself. +1 for the question btw.
I know there some experienced loadRunner users around so I would like to ask (as I was not able to find the answer on my own): Is the content checking available only for webpages? I mean, I cannot check for content in win32 apps, right? Thank you!
If you are asking about using the web_reg_save_param function, then, yes, it is limited to web applications.
Generally, functions with a "web" prefix are unique to web applications.
web_reg_save is web protocol-only, yes.
Depending on the protocol you use, you surely have a way to do a context verification. For example, when you are using terminal emulator, you can check for specific strings in specific display areas. Or, when using Citrix, you can wait for specific bitmaps to appear in certain areas. Or, with RMI, you can inspect whatever you want in the replies you receive.
Inspecting a Win32 app's screen, however, might be painful. LoadRunner tries to "sniff" at the protocol level, so usually you'd have some traffic to emulate on the sockets level, for example. You could still find the app's window handle and fetch some content from it using Windows API calls. LR will not assist you in doing so, though, except for with DLL support.
Is there a way to determine what kind of data plan a device has so an app provides a less rich experience if a data plan is not available? I imagine the connector factory would still be able to return me an HTTPConnection but it would cost the user serious money for lots of data, and I'd like to be nice and prevent that.
I thought there would be a way to query device capabilities in the MIDP API, but maybe it's in CLDC?
Since you mention it in your comments, you can probably make a Symbian OS C++ application that only connects via a specific set Wi-Fi access points (and just stay offline if none of these are available) but I can't think of a way to figure out the current user data plan or whether a given Wi-fi network is free.None of that is available in J2ME, at least not until something like JSR 307 is implemented.
You might want to look into how the Nokia IAPInfo API behaves on actual phones (including Sony-Ericsson and Samsung Series60 phones, potentially) since it is the closest thing to what you want.
No there is no way to do this.
As far as I know there is no way to do this. To address this precise issue, on first download we provide a big bold letter warning saying our apps require data plan. You can do something similar.
Or you can provide an option on first download for the user to say whether he has a data plan or not, and provide a degraded user experience if he doesnt. Dont forget to keep this as an option in application settings and allow the user to enable data services later, as he/she may get a data plan and want to use your app.