For several years, I have handled various administrative requests related to applications created with WPMobile.App. These may involve changing an Android application identifier, updating the associated WordPress website address or transferring a licence to another account.
These operations are generally quite simple from a technical perspective. They do not require developing a new feature and can sometimes be completed quickly. Until now, I handled them free of charge as part of support.
I have decided to change this approach by introducing a dedicated WPMobile administrative change service, priced at €35 excluding VAT per intervention.
The objective is not to restrict WPMobile features or turn a one-time licence into a subscription. It is simply to distinguish normal product functionality from individual operations that require my manual intervention.
Why does an application sometimes need administrative changes?
A mobile application is associated with several technical details when it is created: an Android identifier, an iOS identifier, a WordPress website address and a WPMobile account holding the licence.
These details are normally expected to remain relatively stable. However, a project may evolve, change ownership, move to another domain or encounter difficulties with a developer account.
For example, when a Google Play Developer account is closed and an application can no longer be distributed from that account, it may be necessary to start again with a new Android identifier and create a new Google Play listing.
Another situation occurs when the original WordPress website no longer exists and the licence needs to be reassigned to a different project. Agencies may also need to transfer a licence to a customer, or a website owner may reorganise several accounts.
These are understandable requests. However, they result from changes in how the project is managed rather than a malfunction of WPMobile itself.
Changing the Android package name
On Android, every application has a unique technical identifier, commonly called the package name or application ID. It generally resembles a reversed domain name and allows Google Play to distinguish one application from another.
Once an application has been published, this identifier cannot simply be replaced on its existing Google Play listing. A new identifier generally means a new application from Google’s perspective, with a new listing and publication history.
A change may be requested after a developer account has been closed, when preparing an application for a different account or when an existing project is being replaced.
I can change the identifier used in the WPMobile configuration, but this does not automatically transfer the existing application, its installations or its reviews to a new Google Play listing.
This is an important distinction: changing technical configuration and recovering an already published application are two very different operations.
Changing an iOS application’s Bundle ID
Apple also uses a unique identifier for each application, called the Bundle ID. It associates the application with its technical identity in the Apple Developer ecosystem.
In some cases, reorganising a project or creating a new application requires changing this identifier in WPMobile.
As with Android, changing the Bundle ID does not allow the identifier of an existing App Store application to be freely replaced. A new identifier may require a new listing and a new publication process.
This operation should not be confused with officially transferring an application between Apple Developer accounts. Apple provides a specific procedure for certain transfers without necessarily changing the Bundle ID.
The WPMobile administrative service covers application configuration, not the transfer of an application between Apple developer accounts.
Changing the associated WordPress website address
WPMobile uses an existing WordPress website as the foundation of the application. The website address is therefore an important part of the configuration recorded when the app is created.
When a domain changes or a project moves to a different address, an administrative modification may be required so that the application uses the correct website.
Sometimes the original website has been discontinued and its owner wants to use the licence with another WordPress project. This type of reassignment requires a change to the information associated with the application.
In every case, changing the URL in WPMobile does not constitute a WordPress website migration. The new website must already be available, working correctly and configured as required.
A new address may also affect certain links, authentication processes or external services. These aspects need to be checked separately from the administrative change.
Transferring a licence to another WPMobile account
A WPMobile licence is associated with a user account. Under normal circumstances, it remains attached to that account throughout the project’s lifetime.
However, an agency may want to hand over management to its customer, a company may change its administrator or several accounts may have been created over time.
In these situations, I can transfer an existing licence to another WPMobile account. This is an administrative operation that changes which account holds the licence.
It should not be confused with transferring a published application between Google Play Developer or Apple Developer accounts. WPMobile accounts and app-store developer accounts are independent systems.
Transferring the licence also does not change its terms. Only the account association is modified.
Why charge for these changes now?
For a long time, I performed these changes free of charge because they were small requests I could handle directly through support.
However, even a simple operation takes time. I need to understand the request, identify the correct account or application, check the information provided, make the change and confirm that everything is correct.
A task that takes only a few minutes is not always limited to the clicks required to change a value. It also interrupts ongoing development or maintenance work.
With the number of applications created over the years, these occasional requests now represent enough work that it makes more sense to handle them as a separate service.
I prefer to keep WPMobile features available under the normal licence terms, without introducing additional subscriptions or artificial restrictions, and charge separately for personalised interventions outside the product’s usual operation.
This also makes support costs clearer: customers who never need these changes pay nothing extra, while those requesting a specific intervention contribute to the time required to complete it.
A one-time service priced at €35 excluding VAT
The WPMobile administrative change service costs €35 excluding VAT for one intervention.
It can cover an Android package name change, an iOS Bundle ID change, a WordPress URL update, an email address change or a licence transfer between WPMobile accounts.
During checkout, a dedicated field allows the requested modification and necessary information to be provided. I then review the request and personally perform the change.
The price covers one administrative modification per order. Several separate changes therefore require separate interventions.
This service does not include developing new features, customising the interface or publishing a new version on Google Play or the App Store. For unusual requests involving technical constraints, contacting me before ordering is recommended.
What stays the same for WPMobile licences?
The general WPMobile model remains unchanged. Licences are still available as a one-time purchase, with no mandatory recurring WPMobile subscription required to keep using the application.
Product features are not becoming individually chargeable. There is no need to purchase a service for every WordPress content update or for normal operations already available through the Dashboard.
The new service applies only to specific requests requiring me to manually change the administrative configuration of an application or licence.
I will naturally continue providing technical support for the product. This distinction simply separates assistance with normal product operation from administrative changes requested after the application has been set up.
WPMobile remains based on the same principle: reusing an existing WordPress website to create a mobile application without rebuilding the entire project. When administrative changes become necessary during the application’s lifetime, they can now be handled through a straightforward service with a price known in advance.
