Skip to content
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

Open
1 of 11 tasks
anthonylavado opened this issue Sep 27, 2023 · 21 comments
Open
1 of 11 tasks

Application Process for Samsung TV Seller Office #222

anthonylavado opened this issue Sep 27, 2023 · 21 comments
Assignees

Comments

@anthonylavado
Copy link
Member

anthonylavado commented Sep 27, 2023

In order to publish an application, we'll be following Samsung's official guide: TV Application Publication Process.

Overall Steps:

  • Registration & Upgrade
  • Certification & Verification
  • Release

Submission Process

Registration & Upgrade

Registering Applications

  • Generate Application ID
  • Upload Application Package

Entering Application Information

  • Registering Application Image(Icons, Screenshots)
  • Entering Application Title and Description (We have text we can use)
  • Entering Service Information (We can fill in our contact info)
  • Setting Service Country (We don't plan on any restrictions, all available countries will be allowed)
  • Entering Billing Information (N/A, we will choose "Free")
  • Entering Application Feature Information _(I believe HDR, and Player)
  • Entering Verification Information

Certification & Verification

  • Request Release, which submits for Testing

Release

  • Set Application Status to "For Sale"

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:

  1. Age Rating Policy
  2. Launch Checklist
  3. Application UI Description - ⚠️ This may be the most important step that we need help with. ⚠️

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

@anthonylavado
Copy link
Member Author

To reiterate from #94 (comment), please remember this:

If you want, you can follow along by reacting to that top comment using the reaction button, or clicking/tapping Subscribe.

I would ask that you please do not post in [this] issue, again, to avoid notifying people for no reason. If we need specific assistance on something, we'll create a comment linking to an adjacent issue where we can discuss further.

@Jaba248
Copy link

Jaba248 commented Dec 11, 2023

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

@swarupbc

This comment has been minimized.

@Jaba248
Copy link

Jaba248 commented Jul 8, 2024

Hi Anthony with LG finally being done how should we move forward
I'll go through the list a bit later and see what I can complete

@kraM1tt
Copy link

kraM1tt commented Aug 14, 2024

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

@nhhvhy
Copy link

nhhvhy commented Aug 17, 2024

I'm also happy to help, is there anything that needs to be done ATM?

@BreakingBread0
Copy link

BreakingBread0 commented Aug 29, 2024

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

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

@kraM1tt
Copy link

kraM1tt commented Aug 30, 2024

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

@StrScr
Copy link

StrScr commented Sep 3, 2024

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

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.

@Mezzfitt
Copy link

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?

@AngelSing-Zepol
Copy link

Greetings, there is still no word on a Jellyfin app in the Samsung TV store?

@Mitchell-Faas
Copy link

Mitchell-Faas commented Oct 28, 2024

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:

  • This is an open source project, and there is no active owner of this issue. What that means is that noone is going to tell you what to do, or how you can be useful. You'll have to figure that out yourself.
  • The process linked in the top comment contains the official guidelines. In the top comment, you'll also find 3 requests for assistance on different areas of the process.
  • Some parts of the process can only be done by @anthonylavado, who has access to the samsung account. (@anthonylavado can you confirm if you're still the correct PoC?) When you complete part of the required work, you can ping him with the details and the work, so he can take that part from there.
  • For the parts you can do, you can take ownership, figure out exactly what Samsung needs (see their website), and prepare all the right documents and information. After, you can add the information for it here (or in your own repo), and share your work with the group. If you're able to partake in more items, do so, if you can only pick up one item, that also works.
  • Beware of the ordering of things. Not all your work will remain relevant indefinitely, so you'll want to wait with some aspects until you're relatively far in the process.

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.

@anthonylavado anthonylavado self-assigned this Oct 28, 2024
@UgaitzEtxebarria
Copy link

UgaitzEtxebarria commented Nov 8, 2024

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.

@Mitchell-Faas
Copy link

@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!

@UgaitzEtxebarria
Copy link

UgaitzEtxebarria commented Nov 8, 2024

I don't have a lot of time but I will try to push it until someone with more time comes to relieve me.
Apart from that, as you have seen, i don't have the English level to correct the documentation (this could be a task where people can contribute).

About the system, there are 4 options:

  • Add a folder in this repository: too much noise to download for who just want the code.
  • Add a new repo: I don't know how to create a new jellyfin repo, i think an admin must create It and then we fill it. I contributed in Home Assistant and is how they work, I know that is not the same case but...
  • Use wiki: This option is valid but maybe it doesnt have all the requirement that we need (image management, format, etc). This adds one extra step, format all the text when it is finished.
  • Use external tool: i don't like to use multiple tools for a project, having the knowledge distributed, but being a temp task, this option can be acceptable.

I will let this here, feel free to comment which one could be the best option or to add more options

@pentamassiv
Copy link

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.

@UgaitzEtxebarria
Copy link

I already create the PR here.
I download the ppt that Samsung demands and I distributed in folders. Now, I need to fill it with some examples and for that it will welcome the documentation that was used in LG process for WebOS. Where can I find this documentation and images?

@Mitchell-Faas
Copy link

Mitchell-Faas commented Nov 8, 2024

@UgaitzEtxebarria

I already create the PR here. I download the ppt that Samsung demands and I distributed in folders. Now, I need to fill it with some examples and for that it will welcome the documentation that was used in LG process for WebOS. Where can I find this documentation and images?

The opening comment mentions that the documentation cannot be retrieved and will have to be done from scratch.

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.

@UgaitzEtxebarria
Copy link

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

@eshirvana

This comment has been minimized.

@J-C-B
Copy link

J-C-B commented Dec 11, 2024

any update on this?

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests