-
-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Application Process for Samsung TV Seller Office #222
Comments
To reiterate from #94 (comment), please remember this:
|
Hi was just wondering if you had started on the ui description document I've downloaded the template and had a look through can get that completed for you |
This comment has been minimized.
This comment has been minimized.
Hi Anthony with LG finally being done how should we move forward |
Any way I can help with this? I'm not a developer but can do all the document busy work and submission stuff. Just getting tired of manually updating the builds and having to travel to do it in person for other family members. Thanks |
I'm also happy to help, is there anything that needs to be done ATM? |
This has worked perfectly for me and saved me all the hassles with self-signing: #255 Keep in mind though that this npm package is not published by an official jellyfin account, but by https://github.com/GlenLowland/jellyfin-tizen-npm-publish |
Doesn't work for me, Tizen Tube on Brew works, JF just gives bad gateway. Also it's no where near the conviennce of the native app install, having to launch TizenBrew first which is very slow to start in itself |
That might be useful as an alternative but it's still not as convenient as having the app available natively. Just imagine having to set up the app for various family members on multiple households. It would be so much easier if you could tell them to search for Jellyfin on the app store and just download that. |
Is the requirement to have a complete flow chart of all the menus a normal requirement for TV applications? This seems crazy to me. I have several family members with Samsung TVs. Is there any room to help with this? |
Greetings, there is still no word on a Jellyfin app in the Samsung TV store? |
Hey folks, Thanks everyone for your eagerness to help out. It's clear that getting this one going is on all of your minds! It looks like there is a certain level of wanting to help, but not being sure how, so I want to add some context to help you get started if that's you. To start, a word of order: This is not really an interactive place, and although wanting to help is great, asking for how, or expressing your desire is just going to ping a lot of people without any progress. Your enthusiasm is still appreciated, but these responses create noise, so are best to avoid. When it comes to how to help:
Again, your help is much appreciated. Unfortunately, a lack of staffing means that you need to come in with a lot of initiative and proactiveness if you're looking to help. |
Hi! Another interested person here! Is there a place/folder/repository where we can let the done documentation? That will help to see where we need the contribution, and can be used as template to fill more documents more easily. In addition, we will see if there are some advances in our objetive of having a native app. Sorry for the noise if you think that is not relevant. |
@UgaitzEtxebarria This is super relevant! There currently isn't anything like that. Perhaps you can come up with a system that allows people to contribute smaller parts? If you're willing to take ownership of managing that larger effort and are able to guide people on how to contribute incrementally, I imagine that would speed things up a lot, especially around the application UI description! |
I don't have a lot of time but I will try to push it until someone with more time comes to relieve me. About the system, there are 4 options:
I will let this here, feel free to comment which one could be the best option or to add more options |
Why don't you just fork the project and then create a new branch where you add all the stuff that's needed. You can write a comment here that you are working on it and post a link to your fork. You then create a PR and mark it as a draft. That's the usual workflow here on GitHub and it works quite well. |
I already create the PR here. |
The opening comment mentions that the documentation cannot be retrieved and will have to be done from scratch.
|
We have done all the documentation, it is possible that we need to specify more adding more detailed info, but the main uses are done. How can we start the registration process? If they ask more detailed info we will fill it, but we need some feedback to focus better our objective |
This comment has been minimized.
This comment has been minimized.
Yes there has been a lot of work done - many hours - the work is documented in this pr - #307 - follow there for more granular updates |
In order to publish an application, we'll be following Samsung's official guide: TV Application Publication Process.
Overall Steps:
Submission Process
Registration & Upgrade
Registering Applications
Entering Application Information
Certification & Verification
Release
Assistance Required
Where we tend to slow down is in validating application functionality. Samsung collects all the templates and information required in a section called "Checklists for Distribution". There are three areas:
Age Rating Policy is easy to tackle. When we submit to app stores, we have a dedicated server with content mostly similar to the public Demo Server's TV and Movie libraries. The main change is the movie library contains only the Caminandes Trilogy. This is because it ensure all the demo content is Family Friendly. LG rejected us once for that. We should be able to set app ratings similar to Plex/Emby.
Launch Checklist looks easy enough. It's just making sure we have everything in place.
Application UI Description is the most daunting. We have already documented most TV UI flow for LG, and we can take screenshots/etc for the Samsung template.
Update: There's a document saved in this field, but we don't have the source for it nor can we retrieve it. For safety's sake, we're starting fresh. I'm setting up the dev environment in my computer today.
Last Updated: 2023-10-01, 14:55 EDT
The text was updated successfully, but these errors were encountered: