Publishing and review

Your developer account lives in the developer portal: register your plugins, upload versions, read the report and try them in your own test area.

Account

1. Sign up: choose Create a developer account in the portal. The publisher name appears under your plugins in the store. You accept the developer agreement; sign-in opens once your email is confirmed.
2. Two-step verification: turn it on in My account to upload versions and create command line tokens.
3. Team: the owner invites developers from Team. Only the owner changes publisher details and the team.

Process

1. Code: register the plugin code under Plugins → New plugin. The code is permanent and must match code in the package viswoo-plugin.json. Optionally add a monthly price suggestion and a note to Viswoo.

2. Package: npm run validate and npm run pack. Increase the version number with every upload (major.minor.patch).

3. Upload: from the plugin page in the portal or from the command line:

   VISWOO_TOKEN=vzd_… npx viswoo-plugin publish .

   The package is checked again with the platform rules and ES5 check, and a draft version is created. The version report shows the checks that passed, sizes and permissions added or removed since the previous version.

4. Test area: Install in test area installs the latest upload in your free test customer; Open the test area in the panel opens the panel for that customer. Connect a screen with the browser player or a real device. Draft versions play only in your test area.

5. Submit for review: use Submit for review next to the draft in the versions table and write release notes (what changed, how to try it). Two-step verification is required. A submitted version shows as In review.

6. Review: Viswoo reviews the automatic report, the permission changes since the previous published version and the design standard checklist: are the permissions justified, do settings come from the schema, are kits and states in place, does the screen view open on a real TV and on LG webOS 3.x, is there personal data.

7. Decision: an approved version is published right away; it appears in the store and reaches installed customers. The reason for a rejection is emailed to you and shown under the version on the portal. A rejected version cannot be resubmitted; upload the fix with a new version number.

Versions and customers

• If a new version asks for new permissions, a customer keeps the old version until they approve.
• If you add a required settings field, the customer’s install pauses until it is filled in. Give it a default.
• Viswoo can withdraw a faulty version: customers go back to the previous published version within the permissions they approved. Send the fix with a new version number.
• In an emergency Viswoo can suspend the whole plugin: it plays on no screen and is hidden from the store; installs and data are kept and it comes back when the suspension is lifted. The portal shows it with the reason on the plugin page.
• If a developer account is suspended, members cannot sign in to the portal and tokens stop working; published plugins keep running at customers.
• The plugin code and package format are permanent; changing the code means a new plugin.

Price and billing

The package carries no price. billingUnit says whether the fee is per screen (perScreen), per customer (perTenant) or included in plans (included); you suggest the amount on the portal and Viswoo sets it. Viswoo collects payments and invoices customers.

Revenue and payouts

• Your share: 70% of the line amount excluding VAT on every payment for your plugin (a different share can be agreed in the contract). Payment provider and partner commissions come out of Viswoo’s share. Free plugins and plugins included in plans earn nothing.
• Refunds: if a customer is refunded, your share of the refunded amount is deducted from your balance.
• Statement: the Earnings page on the portal shows the monthly statement (per plugin) and a line-by-line CSV for each month. Months close on Turkey time; customer details are not shown.
• Payout: once the balance of closed months passes 1,000 TRY, issue an invoice to Viswoo for the balance (adding VAT on top) and request a payout on the portal with its number and date. The payout is sent by bank transfer to your IBAN and you are emailed; a balance below the threshold rolls over to the next month.
• Who is paid: only publishers that can issue invoices (a company or a sole proprietorship). Only the publisher owner enters the legal name, tax office and number, address and IBAN under Earnings → Payout details; two-step verification is required and every owner is emailed when they change.

Visibility

The store page is built from the manifest: name, summary, description (Markdown), icon, images, publisher, category and permissions. Viswoo grants the verified publisher badge.

Analytics and reviews

The plugin’s portal page shows counts updated every few minutes: installs (customers who approved the permissions), active (plugin currently on), uninstalls (installed, then turned off) and the average rating. Test areas are not counted. You read store reviews on the same page and reply; your reply shows under the review in the store. The customer who wrote the review is not shown to you.