Following is the URL. I want to play following URL video in my iPhone application. Please help me out to play this
http://www.example.com/SomeVideoOrAnother.m4v
I am building an application where I'll provide user list of movie or advertisement. User will select one of them and redirected to enjoy creative ad.
You seem to not have done any background learning on iOS, judging by the broadness of your question.
I would recommend the Apple Documentation (Getting started) as a good place to start.
Also, see some of these books on Amazon.
To answer you question, there are a few frameworks to look into, for example AV Foundation.
Related
I followed https://developers.google.com/actions/dialogflow/first-app tutorial and built my first google action. The action is working fine on my laptop browser in the test (Followed "Preview the App" section of the tutorial) environment. However, when I am trying to use this action on my phone by saying "OK Google talk to my first app". It's not working. Is it supposed to work on my phone as well? I have logged in with the same Gmail account on my phone also.
PS - I have posted the same question on "actions on google" google plus community google as well but I am not sure if that community is to post such questions or not. Therefore, I am posting it here also.
Thanks in advance!
Once you have enabled testing through the simulator, it should be available on all devices (mobile, speakers like Google Home, etc) with the same account your simulator is running in. Double check to make sure they're the same account.
In your case, however, you may be using the wrong invocation phrase. If you actually said what you did above, you need to say the exact same thing that you typed to invoke it.
If you haven't set a name in the configuration, then that phrase will be
Talk to my test app
Update
As you note in the comments - you also need to make sure you're running the Google Assistant, and not one of the other voice search components. The Google Assistant requires:
Android 6.0 or higher
Google app 6.13 or higher
Google Play services
1.5 GB of memory
720p screen resolution
Phone set to a supported language
As you probably already know you have to enable Web & App Activity, Device Information, Voice & Audio Activity in the Activity controls page.
Then you also have to be sure that the language of your agent is the same used by your google assistant.
I solved thanks this last step.
Hope this helps
have done my due diligence, and not found any other posts that answer this question, but as usual, if you know a similar question, point me that way!
I noticed a long time back that Libspotify has been dicontinued:
(https://developer.spotify.com/technologies/libspotify/)
So, my question is - what should we do for developing Desktop applications?
They do state: "We hope to be able to provide you with a new library for other platforms." But, this has been going on since 2015!
I have seen many projects in GitHub still using Libspotify - so what should we do? An update was promised "in the upcoming months" but I've not seen anything yet.
What should we do for developing Desktop Applications?
We at Spotify don't currently provide playback as part of our platform offering outside of our iOS and Android SDKs, and I don't have any updates on that at the moment. As mentioned on the website, we hope to be able to provide playback SDKs for more platforms in the future. We don't support any new development on libspotify.
You can use the Spotify Web API to interact with Spotify in a variety of ways, including getting information about metadata, and accessing/modifying user libraries and playlists, which may be useful. You can also use the Applescript API to control playback on macOS, which may also help.
The Spotify Web API is pretty straight forward to use. Of course it defines the protocol rather than implements it so it is OS independent.
I put together a few classes to help unwrap some of the JSON parameters simply. These were written in Swift for macOS.
I've started looking into developing Skype Bots and I'm a bit confused on how my bot can respond with something other than plain text. I watched a video on How to build a bot for Skype from the Build 2016 conference and they mentioned something about Visual Cards. Basically a visual card seems to be a clickable image with text and/or a carousel of clickable images. Anyways... I basically want to send the user something nice and pretty that they can click to obtain more information. Thank you for any direction you can give.
Supported capabilities in Skype are shown at https://developer.microsoft.com/en-us/skype/bots/docs. These do not currently include rich cards but hopefully something that isn't too far away.
In Blogger I am trying to recreate the audio feature used in this web site http://www.talkenglish.com/lessondetails.aspx?ALID=2001 where you click on text and hear the audio (an mp3 file) instantly. When I embed identical code into a Blogger page and click it, it wants to play the mp3 file by kick starting Windows Media Player. I don't want a solution like SoundCloud that creates visible player controls. Can anyone suggest a solution. I am hoping to use it to create an online amateur speech therapy package to support some voluntary work I do in this area.
Thanks
That site is using a file called audioplayer.js. To be honest, I am not exactly sure if that's custom built or not. You can look at the source for that here. You have a bunch of options to get the functionality you're looking for. A couple are below.
You can use SoundManager2 which is a very robust JS Sound plugin.
You can also use HTML5's built in <audio> element. You can read more about that here
I was hoping that someone knows a little bit more about Google Plus's in-browser screensharing capabilities. The flow obviously is:
Download some sort of native plugin
Visit the website
Some magic
Bam! There is screenshare
What exactly is going on with the plugin that is downloaded? Where can I look to build a system that works similarly?
All online resources point to taking a screenshot of a person's screen and creating a MJPEG, and we all know that's no fun.