Answers to common questions about AsoTools functionality and security.
Create an App Store Connect API key in Apple Developer, then open AsoTools settings and enter the Key ID, Issuer ID, and the private .p8 key content. AsoTools verifies the credentials, stores them in macOS Keychain, and then works directly with Apple App Store Connect APIs. You can switch keys when you need to work with another account or client.
AsoTools covers the daily App Store Connect work that ASO specialists and release teams repeat most often: app metadata, names, subtitles, descriptions, promotional text, keywords, release notes, localizations, screenshots, app previews, version history, ratings, reviews, and basic release preparation.
AI functions help translate missing localized metadata directly inside the editor. They are designed for App Store fields such as app name, subtitle, description, promotional text, what's new text, and keywords. AI functions require an active device subscription and a separate AI functions subscription for the same device.
No. AI functions speed up first-pass localization and reduce repetitive translation work, but final wording, keyword strategy, legal claims, and market-specific positioning should still be reviewed by a human ASO specialist or product owner before saving to App Store Connect.
AsoTools shows screenshots and app preview videos in an App Store-style media workflow. You can review media by localization and platform, prepare screenshot sets, reorder assets, and work with supported device families. The screenshot section should be used together with metadata and version context so visual assets stay aligned with the release.
App Store Connect allows larger device screenshots to cover compatible smaller devices in specific families. AsoTools exposes that workflow clearly so you can understand which screenshot sets are required and where custom screenshots should override inherited assets.
Yes. AsoTools is built around table-style metadata editing, so you can compare locales, find missing values, edit keywords, subtitles, descriptions, promotional text, and release notes, then save changes in a controlled batch instead of jumping between many web pages.
Yes. AsoTools includes ratings and reviews management with filters by platform, rating, version, review type, and territory. This helps product and support teams inspect feedback without opening multiple App Store Connect screens.
Private App Store Connect keys are stored locally in macOS Keychain. AsoTools is a native macOS application and is designed to keep credentials under the user's control. Avoid sharing .p8 keys in chat, email, screenshots, or support requests.
Demo Mode lets you explore the interface and workflows without connecting real App Store Connect credentials. It is useful for training, screenshots, product demos, and testing the interface before working with production apps.
Yes. You can switch API credentials in settings, which makes AsoTools practical for agencies, freelancers, and teams that manage several App Store Connect accounts. Keep each account's API keys organized and remove unused keys from Apple Developer when they are no longer needed.
The Mac App Store version is installed and updated through Apple review and store mechanisms. The website build is distributed outside the Mac App Store and is intended for direct installation. The current website build is the focus for device subscriptions, balance-based billing, and AI functions.
In the website build, each device can have its own app subscription. A master account can add devices, manage subscriptions, and use one shared balance for subscription charges. If the server cannot confirm subscription data, the app treats the subscription as inactive.
When the balance is insufficient for the next subscription period, the server stops charging and the related subscription becomes inactive. If the main app subscription is cancelled or expires, AI functions for that device are cancelled as well because they require an active app subscription.
The in-app top-up flow creates a support request with the amount selected by the user. Support replies with a payment link, confirms payment after it is received, and the user sees the messages in the app. The balance is credited manually by support after payment confirmation.