DevConsole
OTA APP UPDATES · iOS & ANDROID

A small fix shouldn’t
need a whole new release.

Integration support: DevConsole supplies project credentials and event logging. OTA bundle publishing and delivery require your separately configured update platform; no built-in update distribution engine is implemented.

Update supported parts of your app without submitting a new version to the Apple App Store or Google Play.

Deliver eligible JavaScript fixes, screen changes and assets through a compatible update integration. Keep customers on your latest supported experience without asking them to download a new store version.

Create account & choose a plan Explore plans →
Requires an update SDK already included in your app. Native changes and changes requiring store review still need a store release. Delivery timing depends on connectivity and your app’s update settings.
Illustrative iPhone and Android coffee app mockups: initial installation from App Store or Google Play, followed by a compatible OTA update. Native changes still need a store release.

Illustrative mockups · App Store and Google Play are third-party platforms. No affiliation or endorsement.

SEE THE DIFFERENCE

One installed app.
Two ways to release a change.

A NEW NATIVE VERSION

Build → Submit → Review → Store update

App StoreGoogle Play

Use the store release process for native code, new permissions, SDK changes and other changes requiring review. Customers install the new version through the store.

AN ELIGIBLE OTA CHANGE

Fix → Publish → App checks → Apply

JavaScript fixesExisting screensAssets

Your already-integrated app retrieves a compatible update through its update engine. No new store download is needed for that eligible change.

Requires a compatible runtime. Update timing and store policy restrictions still apply.
WHAT YOU CAN UPDATE

Fix the details.
Keep your app moving.

Supported app fixes

Correct eligible JavaScript bugs within the capabilities of your installed app runtime.

Existing screens and interface

Adjust supported layouts, text and styling without rebuilding the native application.

Images and assets

Deliver compatible asset changes as part of your update integration.

A SIMPLE EXAMPLE

A broken button.
A supported fix.

Your app is already installed. A bug in its existing JavaScript flow stops a button from working. Your developer fixes the code and publishes a compatible OTA update through your connected update platform.

The app checks for updates and applies the fix according to its configured update behavior—often on a subsequent launch. The customer does not need a new store download for that eligible change.

Already installed app

Fix → Publish → App checks → Update applies

No new store version for an eligible change

No request for the customer to reinstall

Existing native runtime stays in place

SETUP & DELIVERY

Connect once.
Publish supported changes.

  1. 1

    Prepare your app

    Your developer integrates a compatible update SDK and publishes the initial app build through the normal store process.

  2. 2

    Choose your plan

    Select monthly or yearly paid access for one project. Review your price and invoice.

  3. 3

    Connect your update platform

    Create your DevConsole project and service key. Configure your app’s update engine and publishing workflow; credentials alone do not install an update engine.

  4. 4

    Publish a compatible update

    Prepare and test the change through your update platform. Your app retrieves and applies it according to its update configuration.

KNOW WHAT NEEDS A STORE RELEASE

OTA for supported changes.
Store releases for native changes.

OTA may be suitable

Eligible fixes, adjustments to existing screens and assets that your installed runtime can support and store policies permit.

A new build is required

Native code or modules, SDK changes, new permissions, runtime changes and other changes requiring Apple or Google review.

Your workspace, ready to connect.

Service credentials

A project API URL and one active key per service. Revoke the current key before generating a replacement.

Basic or Production

Basic is intended for testing your integration in development or staging. Production is intended for your live, customer-facing app.

Monthly or yearly one-time purchases for one project, with no automatic renewal on new purchases. Final prices are shown in Plans.

Clear billing

Confirmed payment unlocks your paid plan and generates an invoice. KWD displays are estimates; checkout is charged in INR.

Questions before you start?

Will every update avoid store approval?

No. Only eligible changes supported by your installed runtime and permitted by store policies may use this path. Native changes and changes requiring review need a new store release.

Is delivery instant for every customer?

No. Updates depend on connectivity, app update checks and when your integration applies them. Some configurations apply an update on the next app launch.

Does this work with every app?

No. Your app needs a compatible OTA runtime and SDK. An existing app without that integration needs a new app build first.

Does buying a plan build the update system for me?

No. DevConsole provides the project workspace, credentials and service access. Your developer must configure a compatible update engine and publishing workflow.

Is a free trial available?

New accounts do not receive a free trial. Choose a monthly or yearly paid plan. Contact info@devconsole.top before purchase if you need help assessing your integration.

Make your next supported fix
a smaller release.

Explore OTA App Updates for your project.

Choose your plan

Ask about your app’s integration →