I am very new to coding and tech talks but I am working with a client who needs help on how to get their OTT app on major ISPs'set-top boxes. Anything around app SDK for specific ISPs, examples on how Dysney+ or Netflix get their app on boxes, which ISP uses which language, which technology do ISPs uses to charge application on their boxes (qml, HTML, ? ) would help me a lot! Apologies if my question is very generic but I don't understand much on this subject.
Thank you very much in advance for your time and help.
When you mention 'ISP' set-top boxes, I assume you're asking how to get the app on the box people get when they sign up for cable TV. For example, if you want your client's app pre-installed on the Comcast Xfinity set-top box, you should contact Comcast so they can provide instructions to make your request.
If you're referring to how you can get your client's video app on common OTT devices such as Roku, you should search that device's website on how to create a developer account. For example, here are details on how to create a Roku channel (app) that people can download onto their Roku device at home.
https://developer.roku.com/docs/developer-program/publishing/channel-publishing-guide.md
When your channel is tested and ready to deploy, you publish it using the Developer Dashboard. If the channel is a public channel that will be offered on the Roku Channel Store, it will be reviewed by Roku during the certification process. If you are updating an existing channel, you will also publish it using Developer Dashboard.
Prerequisites and guidelines for creating a public channel
To assure success in creating a public channel, you will need to:
Create your design assets following Design and User Experience Guidelines.
Go through the Pre-certification Check List.
Package your Roku channel.
Publish your channel (this page).
Cheers.
Related
With Apple getting ever more stringent by enforcing 2FA on all iOS accounts, a unique challenge that we've encountered is how to setup a system where Apple’s 2FA codes for a shared dev account can be forwarded to perhaps our private slack channel? Hence enabling multiple members on a team access to Apple’s services.
I got so annoyed by this that we then developed a hack.
It’s a Python script that’s running in a terminal on the mac mini CI machine and using some vision SDK tooling, checks the screen every few seconds for the 2FA dialog pop-up.
If it finds it, it then navigates the pop-up, crops the 2FA code, does OCR on it, and relays the code through the Slack API to a dedicated internal buildbot channel that our devs get notified on.
Sample cropped 2FA code screenshot:
The result, is the general shared apple id account is now much more convenient and efficient to access by our devs for CI/CD or any other client App Store info updates.
So that’s one way to do it. 😎
I am new to iOS Development and am working on an app concept for a customer. The user experience could be greatly improved if the app was able to intercept a deep link.
This is possible in android since links are not bound to the website but to the app manifest itself. So if I make an app that can receive Amazon links, then the user can choose which app opens those links.
Is this possible on iOS using Apple deep links? I am aware they are more complicated since they require a component on the website itself. Furthermore, the app won't need to receive Amazon links if the Amazon app is installed.
I would attempt this myself but do not have an Apple Developer Account yet and don't want to invest without knowing the answer.
The only universal (deep) links you are able to hear about are those directed to your own domain. You cannot receive an Amazon link, because (unless you are Jeff Bezos in disguise) you don't own the amazon.com domain.
I use Firebase database, storage etc. in my application. When I uploaded my archive to Itunes Connect, it has asked me a questions about crypting. Do I use crypting in my application and etc.
I know, that Firebase uses https.
So the question is: If I use Firebase, what should I answer on this questions?
As of September 20th, 2016 (Dentons) the answer is almost always No. Unless you are a encrypted message provider like Signal, Telegram, Whatsapp or Snapchat - these export controls are no longer a concern. Nearly every app uses HTTPS these days and it defeats the purpose of the U.S. Export Registry if every app needs to be registered.
The countries that are export restricted are people you don't normally want as customers; Syria, North Korea ect... and are typically restricted from using apps for more fundamental reasons - like not having cellphone towers or even the ability to buy a cellphone. It is common for backend services like Firebase and Google to blacklist export-restricted IP spaces, so they won't be able to connect even if they get the app.
It's not immediately clear from their site, but can one build a one to many streaming app like Ustream using TokBox web/iOS APIs? Is it limited to just chat.
I'd want to make something that captures video from the desktop or ios device and makes that video accessible at some public URL.
Yes that is capable. OpenTok works with Publishers and Subscribers. A single Publisher can publish to a session then many users can subscribe to the publishers stream using a public access token.
Check out the API it shows what you can do with it, how it does it and even shows some good demos. There are many examples of how they have used it for online chat shows and other similar one-to-many applications.
They've also very recently released their WebRTC version which makes it definitely worth a look!
We've written an app for our clients that connects to external hardware over Wifi (hardware designed by our client). My question is, how do we go about submitting this for review? The software won't do very much without the hardware. Just to be clear, the hardware does not connect directly to the iPad with a cable, it connects over WiFi only.
I just want to get some clarity on what we need to do to get this app through the review process and into the App Store.
Any insight will be appreciated.
I'm one of the authors of StageMix for M7CL, LS9 and CL and it has exactly this issue - the hardware it works with is a somewhat expensive dongle ;)
We added disconnected demo mode where all of the application's UI works - only difference is that nothing is remote controlled. This has the added benefit of allowing customers to try the app out when the hardware isn't handy.
Apple has always been happy reviewing the demo mode and presumably never tested it connected.
I do suggest that the iTunes Store metadata for the App - and if possible the user interface - is very clear about the external hardware requirements
One of my recent updates to DAQ-app failed approval with a note that I needed to show a video of it working with the hardware.
My demo mode let them test some functionality, and the video showed the connectivity. I just hosted the video as a private video on YouTube, and it was accepted quickly after I submitted the video.
The next update was accepted with the same video and a note that there were only minor changes, and no changes to the connectivity.
I emailed Apple this week to ask what their current policy on this is, and they said we have to ship the hardware to them. They also said they can return it if needed, but that we'd have to ship the hardware to them again for every future app update too.
I had same experience. our App is
http://itunes.apple.com/us/app/jia-jia-yi/id497092682?mt=8.
This app also works with a device.
But we was lucky, apple did not ask us to support the hardware to them.
Hope you are lucky too.
:)
Apple required me to send in hardware
We recently submitted an app that required our hardware to be submitted too. The address it was asked to be shipped to is:
Apple, Inc.
1 Infinite Loop, M/S: 124-2APP
Cupertino, CA 95014
USA
It's probably best that you submit the app first and let it get stuck on that process so when you send it in, you can direct it to the proper person in charge. As for FCC, you need to fill out this form if shipping from outside US:
http://transition.fcc.gov/Forms/Form740/740.pdf
Other notes provided by Apple:
A separate FCC Form 740 must be used for each different radio-frequency device or component in the shipment; however, a form is not required for subassemblies, parts, or components of radio-frequency devices.
The form may be completed by the shipper or recipient, but if the form is not sent with the original shipping documents by the shipper, the shipment may be delayed in customs.
Ensure all serial and ID numbers are available as well as the name and address of the original manufacturer.
I hope that helps!