Who does what on the LG route
Three parties touch an LG channel app. You own the store listing, we produce the package, and LG reviews and publishes it. Knowing the split saves you hunting for a certificate step that does not exist.
| Item | Who handles it | What to check |
|---|---|---|
| Seller Lounge account | You, at seller.lgappstv.com | Profile complete, individual or corporate seller chosen |
| The webOS package (.ipk) | Built in your panel under Build your apps | Latest build downloaded, uploaded as built |
| App ID | Shown in the panel's Store identifiers | Same ID typed into Seller Lounge as the package declares |
| Signing | No step on your side | The webOS tools have no signing step; upload the .ipk as built |
| Self-checklist and UX scenario | You | Checklist template downloaded on the day you submit |
| QA and publication | LG | Answer any queries inside Seller Lounge |
The TV app is part of the PRO and Platinum plans of our live video streaming service, alongside the HLS player and the encoder ingest. The free plan carries the channel and the player, without the TV apps. The package targets webOS 4.x and later, which means LG sets from 2018 onward.
What to have on the desk before you start
Gather these before you open Seller Lounge. LG's preliminary document review turns apps back for missing or incomplete paperwork (no self-checklist results, no UX scenario, an icon off guideline) before any technical test.
- The .ipk: the current LG build from Build your apps. If you changed the channel's name or artwork since the last build, rebuild first.
- The store images: the icon
lg/icon-400x400.pngand the backgroundlg/background-1920x1080.jpg, both in the store images zip. - Screenshots: the main and additional images Seller Lounge asks for, taken from the running app in the webOS TV Simulator or on an LG set.
- Listing text: description and category, written for viewers, not for the reviewer.
- Privacy policy URL: generated per app in your dashboard, under Publish in the stores.
- The self-checklist and UX scenario: covered in their own section below.
The app ID is permanent. LG's own reference states it cannot be changed once the app is published, so confirm the Store identifiers value before the first submission, not after.
The submission, in order
- Register. Create a seller account at seller.lgappstv.com for yourself or for your organisation, then complete the profile.
- Download the package. In your panel, build LG under Build your apps and download the .ipk. Upload it as it is.
- Open a new app registration. Where Seller Lounge asks for the app ID, paste the webOS ID from Store identifiers. It has to match the ID inside the package's
appinfo.json. Upload the .ipk. - Add the listing. Upload the icon, the background and the screenshots, then the description, the category and the privacy policy URL.
- Attach the paperwork. Upload the self-checklist filled in with your own results and the UX scenario.
- Submit for QA. From here LG tests the app on its own TVs. Watch Seller Lounge for questions and reply there.
How to confirm it worked: the app shows as submitted, then in review, in your Seller Lounge app list. When it passes, it appears on LG's app store under your seller name. Seller Lounge relabels screens between site revisions, so go by what a screen is for rather than its exact title; the LG Seller Lounge runbook describes each step by its purpose.
The two documents QA reads first
LG says plainly that an app arriving without its self-checklist form, or with too little in it, is rejected. Its FAQ adds that a checklist on an earlier template version will not be approved. Treat both documents as part of the build.
The self-checklist. Download it from Seller Lounge on the day you submit; a copy kept from a previous round is the classic avoidable rejection. It has three parts: content, UX, and privacy and credentials. The UX items LG marks as mandatory include:
- every navigation key works in the app: the four arrow keys, OK and Back;
- the screen pointer of the Magic Remote works everywhere;
- every selectable object shows a visible focus effect;
- on webOS 23 to 25, Back on the app's first screen returns to the Home screen.
The UX scenario. This is the tester's map, and LG asks for it to be as accurate and detailed as possible. Describe the screen flow and what each key does. For the channel app the screens are Home, Live, the video detail page, the video player, Search and About, plus the exit dialog. Say outright that focus moves with the D-pad throughout, that the Magic Remote pointer is supported, that Back goes up one level, and that there is no login.
Optional: run the package on your own LG set
You do not need to sideload the app to publish it, but seeing it on a real set before QA does is the cheapest check there is, and it gives you screenshots. LG's tools for this are the webOS CLI and the Developer Mode app.
- Install the CLI on a computer on the same network as the TV. LG recommends Node.js 14.15.1 to 16.20.2. Run
npm install -g @webos-tools/cli, thenares -Vand check it prints a version. - On the TV, install Developer Mode from LG's store, sign in with your LG Developer account, and switch on Dev Mode Status. The TV reboots.
- Run
ares-setup-device, choose add, and enter a name, the TV's IP address, port 9922 and the user prisoner. Check withares-setup-device --list. - In the Developer Mode app, press Key Server. Run
ares-novacom --device tv2 --getkeyand type the six-character passphrase the TV shows (it is case sensitive). Confirm withares-device --system-info --device tv2. - Install and start the package:
ares-install --device tv2 ./com.domain.app_0.0.1_all.ipkand thenares-launch --device tv2 com.domain.app, using your own file name and app ID.
Replace tv2 with the name you gave the TV in step 3. Developer Mode runs for a limited session shown as Remain Session; extend it with EXTEND while it is still live. If it lapses, LG turns Developer Mode off at the next reboot and removes the test apps.
How LG reviews the app, and how long it takes
LG runs three checks: a pretest of the information you submitted, a function test that the app works without errors, and a content test for inappropriate material. A failed app comes back with a list of issues; fix them and resubmit.
Plan in weeks. LG's Seller Lounge FAQ puts the average QA at two to three weeks and warns that it can take longer when many apps are waiting, so do not tie a launch announcement to a date. It helps to have something playing on the channel while the review runs, so the Live screen has a picture to show; live video ingests RTMP from a hardware encoder or from OBS, vMix and Wirecast, as the live video streaming service page explains.
Updates after launch
Approval covers the version LG tested. A new package goes through review again: rebuild LG in the panel, upload the new .ipk with a fresh checklist where Seller Lounge asks for one, and resubmit. LG will not accept the same version number twice, so always upload the newest build. What the app plays comes from your channel's feed, so new videos, programmes and links reach viewers without any store update at all.
When it goes wrong
- Rejected at pretest: check the checklist template is the current one, every screenshot slot Seller Lounge asks for is filled, and the privacy policy URL opens.
- App ID mismatch: the ID typed in Seller Lounge differs from the one in
appinfo.json. Copy it again from Store identifiers. - Focus or Back findings: describe the key behaviour exactly in the UX scenario, and test each screen with arrows only, then with the pointer only.
- Developer Mode will not connect: confirm the TV and computer share a network, the port is 9922, and the session has not expired.
- A QA report you cannot map to the app: our support is on chat around the clock, or email support@getstreamhosting.com, and a second reader often spots the item.
The other stores follow the same rhythm with different paperwork; the publishing guides cover each, including the Samsung Seller Office route for Tizen sets.