Prepare. Review. Publish.
Listlane is a Node.js CLI and web dashboard in development. Public npm installation and hosted signup are not open yet. This documentation introduces the current product workflow; signup and payments are not open.
Before you begin
A reference for the requirements described in this guide. Public installation and hosted signup remain closed.
| Area | Prepare | Read next |
|---|---|---|
| Local workspace | App configuration, localized copy and artwork. | Workspace |
| Store accounts | Your own Apple Developer and Google Play accounts, app records and operation-specific API permissions. | Accounts |
| Local CLI | Node.js 22.13 or later; installation instructions follow verified npm publication. | Access requirements |
| Artwork | Screenshots organized by platform, language and device. | Artwork review |
Prepare a workspace
Listlane combines a Node.js CLI with a web dashboard for App Store and Google Play release work. A workspace holds your app configuration, localized metadata, and artwork. The dashboard images on this site show the current product using Sky Journal, a fictional example app.
Connect your store accounts
You will need your own Apple Developer and Google Play developer accounts, existing app records, and API credentials with the permissions required for each operation. Listlane does not create developer accounts or replace store enrollment, app signing, or review requirements.
Prepare listing copy
Edit localized titles, descriptions, and other supported fields with length checks and illustrative store previews. Optional AI assistance can draft or adapt copy from your app facts. Review each suggestion before applying it to your workspace.
Review artwork and differences
Organize screenshots by platform, language, and device. Inspect image formats and dimensions, review imported artwork, and arrange the order. Review listing differences before a store update; a workspace save does not publish your changes.
Make an explicit publishing decision
The CLI provides command help and a dry-run mode for supported publishing operations. The dashboard separates preparation from submission. Store API permissions, signing requirements, and review rules still apply; Listlane does not guarantee store approval.
What stays in the consoles
Create app records, complete Apple App Privacy, and manage Google Play custom store listings in their respective consoles. Some release, pricing, and availability decisions also require console work. Supported workflows and their limits will be documented with the public release.
What does each release state mean?
A saved change, a store submission and a public update are different milestones. Open a stage to see what it means and what to check next. This guide describes the workflow; it does not show a live status for your app.
Saved in your workspaceLocal preparation
Your copy and artwork are prepared in the workspace. Saving here does not send an update to either store.
Next: Review the listing differences, languages and artwork.
Dry run reviewedLocal preparation
For supported publishing operations, a dry run lets you inspect the intended action before running it. It does not submit the update for store review.
Next: Confirm the intended app and changes, then make the publishing decision.
Uploaded to a storeStore processing
The selected files or metadata have reached the store. Processing and any required review are separate steps; an upload alone does not establish public availability.
Next: Check the operation result and store status before taking the next action. Store requirements and supported operations vary.
Submitted for reviewStore review
The update has entered the store's review process. Submission does not guarantee approval, and an approved update may still be waiting for its configured release.
Next: Follow the review outcome and confirm the release settings for that store.
Publicly availablePublic distribution
The intended update can be found on the public store in its configured regions. Availability may differ by platform and rollout settings.
Next: Verify the public listing and version for the audience you intend to reach.
Public Listlane installation and hosted access are still closed. Check the current access requirements.
Compare the milestones
Use the stage to choose the next check. These are explanations, not live results for your app.
| Milestone | Where it stands | Next check |
|---|---|---|
| Saved | Prepared in the workspace. | Review copy, languages and artwork. |
| Dry run | Intended operation inspected; no review submission. | Confirm the app and the intended changes. |
| Uploaded | Files or metadata reached the store; processing may remain. | Read the operation result and store status. |
| Submitted | In store review; approval and release are separate. | Follow the review and configured release settings. |
| Public | Available in the intended store regions. | Verify the public listing, version and audience. |
Getting started: availability and requirements
Local CLI
Public installation not open
The CLI requires Node.js 22.13 or later. Installation instructions will appear after npm package publication is verified.
Understand a local workspaceHosted dashboard
Hosted service coming soon
Hosted signup and payments are not open. Access details will appear after the service and its policies are ready.
Explore the dashboard workflowThe CLI requires Node.js 22.13 or later. Public npm installation instructions will appear here after package publication is verified. Hosted dashboard access and service policies will be published when their launch requirements are complete. This site currently provides product information without signup forms, payments, or an email waiting list.
What can I prepare while access is closed?
- Collect the app facts and localized copy you want to review.
- Organize screenshots by device and language.
- Identify the store account owner and the publishing permissions you will need.
This checklist does not connect an account, create a workspace or submit a release.