Once all your plugins are supported in one way or another (Capacitor plugin or compat for Cordova plugin) you should just be able to install Capacitor in your project and see if it all works. Required code modifications in your app should be limited to the interaction with native.
I've come to _expect_ that Netflix probably doesn't have a classic I particularly want to watch. Anecdotal, sure, but I find that I treat Netflix and <music streaming service of choice> differently. With Netflix I'll turn it on when I want to watch something but I'm not sure which. If I have a show/ movie in mind I'll check if it's there but generally I expect to pay a small fee to rent it on Amazon. The catalog changes monthly, so you never quite know what is going to be there on any given month. With music I know that the music I'm looking for is (probably) there and I won't have to pay more for it.
They are both media-consumption services but I think most people treat them like
Great looking service, excited to check it out further. The company I work for builds lots of self service video portals for clients and we use Azure Media Services for ingestion, transcoding, storage and streaming.
Care to elaborate on how this related to Azure Media Services?
Thank you! Sounds like a great fit, ping me if you have any questions down the road (my email is just matt at our domain).
Azure Media Services (and other, similar products such as Amazon's media offerings, etc) is a suite of products that ultimately take you from ingesting a video to playing it back, but you're going to do a lot of gluing together parts to get there. While gluing those parts together you're making a lot of decisions around formats, encoding, etc, and let's be honest...those probably won't get revisited soon enough. Our system makes those decisions on the fly based on actual performance data for your viewers.
When you ingest an asset into Mux, we give you a playback ID that's playable in seconds (which, at least imo, is very cool on its own), and you can just use that in your players and go back to making amazing video portals. You can also use that same ID to do things like request smart thumbnails immediately (had to plug that because I spent _way_ too much time on that part of the marketing website).
We do some really cool things behind the scenes around how we encode the assets just-in-time, CDN switching, etc, but ultimately the goal is that you can just wire our API into your CMS and think less about encoding minutia.
I think there are a lot of individuals that preach things like the 4HWW when trying to achieve a wealthy lifestyle with little or no work, but the author is just taking advantage of that.
Work smarter not harder, and it doesnt make you a craftsman by working slower or over longer periods, its about optimizing your time and being as effective as possible. Much of a typical 40hr work week is wasted time.
I think we need to be careful about integrating blockchain into the fabric of societies, especially the social and emotional aspects.
'Think not of how to replumb or rewire the world, but how to create the environment where interactions can be different, social, within a new economic order.'
This gets me thinking of the episode Fifteen Million Merits (S1, Ep2) of Black Mirror.
Pretty simple use case but I integrated the Cognitive Service API with a simple personality quiz app that allowed the user to upload their photo to determine gender and age in addition to the questions they answered that helped determine who they got matched up with.
Very simple REST API, I was able to mock everything up with POSTMAN(chrome rest app) then quickly port the calls to PHP code making simple curl requests.
