Dublicate Talking Statues native app for iOS and Android
Budget / Salary$250–750
TypeFreelance project
LocationRemote
Posted1 hour ago
The existing iOS application and current Android version will be used as the primary references. I’ll review the live apps, map the complete user flow, inspect the supplied source code and assets, and examine how both apps communicate with the backend.
The goal is to create a separate version of the product under a new name while preserving the existing experience. No new features or design changes are required at this stage. Every screen, interaction, piece of content, backend function, and supported workflow should operate correctly across both platforms.
Scope of Work
The project will include:
Reviewing the live iOS and Android applications
Reviewing the complete iOS and Android source code
Duplicating and configuring the backend used by both applications
Duplicating the backend database, APIs, files, media, scheduled tasks, and related services where required
Configuring the new apps to communicate with the duplicated backend
Preserving the existing functionality and content
Reproducing all screens, navigation, interactions, animations, and media
Updating the app name, bundle identifiers, package name, icons, launch assets, and store metadata
Configuring separate production and testing environments where appropriate
Testing communication between both apps and the duplicated backend
Verifying authentication, data retrieval, uploads, notifications, media, location features, analytics, and other integrations used by the existing system
Checking security, permissions, privacy disclosures, and platform-specific requirements
Preparing release builds for both iOS and Android
Uploading the apps to the appropriate developer accounts
Supporting the review and approval process for both stores
Deploying and verifying the duplicated backend in its production environment
Backend Duplication
The backend will be treated as a core part of the project rather than an afterthought.
The work will include reviewing the existing backend architecture and identifying all services required by the apps, including APIs, databases, storage, media files, authentication, scheduled jobs, administrative tools, third-party integrations, and configuration variables.
Where appropriate, the existing backend will be duplicated into a separate environment so the new apps can operate independently from the original applications. The duplicated environment will be configured with the correct database records, content, media, credentials, domain settings, API endpoints, security rules, and application settings.
The backend will then be tested with both the iOS and Android builds to confirm that the apps can reliably connect, retrieve and submit data, load content, handle user actions, and maintain the expected behavior throughout the complete user flow.
The original backend must remain protected during this process. Any production changes will be planned carefully to avoid disrupting the existing apps.
Deliverables
The project deliverables will include:
A clean and maintainable iOS project configured for the new app identity.
A clean and maintainable Android project written in Kotlin or Java.
A duplicated and configured backend supporting both apps.
A duplicated database, storage, media, APIs, scheduled processes, and related services where required.
Production and testing configuration for the new app ecosystem.
A signed Android App Bundle (.aab) ready for Google Play.
The Android keystore and signing information required for future updates.
A release-ready iOS archive prepared for App Store submission.
Updated app names, identifiers, icons, launch assets, and store metadata.
Backend deployment and configuration documentation.
App setup, build, signing, and release documentation.
Uploading and testing of both apps.
Testing and verification of the duplicated backend.
Step-by-step support through App Store and Google Play review.
Post-submission verification that both apps are available and functioning correctly after publication.
Testing and Quality Assurance
Testing will cover the complete system, not just the app interfaces. This will include:
iOS and Android installation and launch
Navigation and screen transitions
User interactions and content display
API requests and responses
Database reads and writes
Media and asset loading
Authentication and account behavior, if applicable
Location, mapping, audio, video, or notification features, if applicable
Offline and poor-connection behavior
Device and screen-size compatibility
Permissions and privacy behavior
Backend error handling and logging
Production configuration
App Store and Google Play release builds
End-to-end testing between both published apps and the duplicated backend
The objective is to verify that the duplicated system works reliably from the user’s device through the backend and back again.
The apps
https://apps.apple.com/us/app/talking-statues/id1391443988
https://play.google.com/store/apps/details?id=com.talkingstatues&hl=en
Duplicate talking statues app and backend
Duplicate app should be placed in same account at Google Play and Appstore
Duplicate backend same hosting at Godaddy - all statues, cities, users, etc should be deleted, so the app is clean and ready to work with new client with new name.
Talking statues credited as delivery more will specify
Languages (update and activate)
The app’s language should be in English and Dutch.
At the moment, some parts of the app are displayed in Spanish. These should be changed to Dutch everywhere, including:
Backend fields
Menus within the app
Notifications displayed on the user’s mobile phone after downloading the app
Buttons and other visible text
Four buttons need to be updated. This includes both the English and Spanish versions currently used in the app. All four buttons should be available in Dutch.
Language Selector (update and activate)
Users should be able to select the app’s language in two places.
During Download or First Setup
When the app is downloaded and opened for the first time, the user should receive a notification or language-selection prompt. The user should be able to select a preferred language at this stage.
In the App Menu
Users should also be able to change the language later through the app’s menu.
The selected language should apply consistently throughout the app, including:
The default language should be English. Dutch should be available as an alternative. When Dutch is selected, all available text and audio should be presented in Dutch.
Audio Player (update and activate)
The audio player should be redesigned to make it more visible and easier to use. It should be clearly recognizable when users open a statue’s information page.
The player should include familiar controls, such as:
Play and pause
Progress bar
Current playback time
Total audio duration
Volume control, where supported
The audio player should retrieve and play the correct audio file from the backend based on the language selected by the user.
Automated Calls
The app will keep using GPS for automated calls.
User can also start the audio player from the statue’s information page.
Listen to the relevant audio using the visible audio player.
The user must manually select the statue or location. The app should not automatically detect the user’s position or start an audio file automatically.
Audio Language (update and activate)
The audio player should follow the language selected by the user.
The default language will be English. If the user selects Dutch, the audio player should retrieve and play the Dutch audio file from the backend.
The selected language must apply consistently to:
Statue information
Buttons
Menus
Notifications
Audio-player controls
Audio content
If an audio file is not available in the selected language, the app should display a clear message or use the default English audio, depending on the agreed product requirements.
NB - we want to make sure that it is possible to dublicate the app in the account for a new project and therefore, we want this done to start with, to solve any issues there may be.
Payment 3 milestones
1st 40% start
2nd 40% upload works
3rd 20% check 14 days
The goal is to create a separate version of the product under a new name while preserving the existing experience. No new features or design changes are required at this stage. Every screen, interaction, piece of content, backend function, and supported workflow should operate correctly across both platforms.
Scope of Work
The project will include:
Reviewing the live iOS and Android applications
Reviewing the complete iOS and Android source code
Duplicating and configuring the backend used by both applications
Duplicating the backend database, APIs, files, media, scheduled tasks, and related services where required
Configuring the new apps to communicate with the duplicated backend
Preserving the existing functionality and content
Reproducing all screens, navigation, interactions, animations, and media
Updating the app name, bundle identifiers, package name, icons, launch assets, and store metadata
Configuring separate production and testing environments where appropriate
Testing communication between both apps and the duplicated backend
Verifying authentication, data retrieval, uploads, notifications, media, location features, analytics, and other integrations used by the existing system
Checking security, permissions, privacy disclosures, and platform-specific requirements
Preparing release builds for both iOS and Android
Uploading the apps to the appropriate developer accounts
Supporting the review and approval process for both stores
Deploying and verifying the duplicated backend in its production environment
Backend Duplication
The backend will be treated as a core part of the project rather than an afterthought.
The work will include reviewing the existing backend architecture and identifying all services required by the apps, including APIs, databases, storage, media files, authentication, scheduled jobs, administrative tools, third-party integrations, and configuration variables.
Where appropriate, the existing backend will be duplicated into a separate environment so the new apps can operate independently from the original applications. The duplicated environment will be configured with the correct database records, content, media, credentials, domain settings, API endpoints, security rules, and application settings.
The backend will then be tested with both the iOS and Android builds to confirm that the apps can reliably connect, retrieve and submit data, load content, handle user actions, and maintain the expected behavior throughout the complete user flow.
The original backend must remain protected during this process. Any production changes will be planned carefully to avoid disrupting the existing apps.
Deliverables
The project deliverables will include:
A clean and maintainable iOS project configured for the new app identity.
A clean and maintainable Android project written in Kotlin or Java.
A duplicated and configured backend supporting both apps.
A duplicated database, storage, media, APIs, scheduled processes, and related services where required.
Production and testing configuration for the new app ecosystem.
A signed Android App Bundle (.aab) ready for Google Play.
The Android keystore and signing information required for future updates.
A release-ready iOS archive prepared for App Store submission.
Updated app names, identifiers, icons, launch assets, and store metadata.
Backend deployment and configuration documentation.
App setup, build, signing, and release documentation.
Uploading and testing of both apps.
Testing and verification of the duplicated backend.
Step-by-step support through App Store and Google Play review.
Post-submission verification that both apps are available and functioning correctly after publication.
Testing and Quality Assurance
Testing will cover the complete system, not just the app interfaces. This will include:
iOS and Android installation and launch
Navigation and screen transitions
User interactions and content display
API requests and responses
Database reads and writes
Media and asset loading
Authentication and account behavior, if applicable
Location, mapping, audio, video, or notification features, if applicable
Offline and poor-connection behavior
Device and screen-size compatibility
Permissions and privacy behavior
Backend error handling and logging
Production configuration
App Store and Google Play release builds
End-to-end testing between both published apps and the duplicated backend
The objective is to verify that the duplicated system works reliably from the user’s device through the backend and back again.
The apps
https://apps.apple.com/us/app/talking-statues/id1391443988
https://play.google.com/store/apps/details?id=com.talkingstatues&hl=en
Duplicate talking statues app and backend
Duplicate app should be placed in same account at Google Play and Appstore
Duplicate backend same hosting at Godaddy - all statues, cities, users, etc should be deleted, so the app is clean and ready to work with new client with new name.
Talking statues credited as delivery more will specify
Languages (update and activate)
The app’s language should be in English and Dutch.
At the moment, some parts of the app are displayed in Spanish. These should be changed to Dutch everywhere, including:
Backend fields
Menus within the app
Notifications displayed on the user’s mobile phone after downloading the app
Buttons and other visible text
Four buttons need to be updated. This includes both the English and Spanish versions currently used in the app. All four buttons should be available in Dutch.
Language Selector (update and activate)
Users should be able to select the app’s language in two places.
During Download or First Setup
When the app is downloaded and opened for the first time, the user should receive a notification or language-selection prompt. The user should be able to select a preferred language at this stage.
In the App Menu
Users should also be able to change the language later through the app’s menu.
The selected language should apply consistently throughout the app, including:
The default language should be English. Dutch should be available as an alternative. When Dutch is selected, all available text and audio should be presented in Dutch.
Audio Player (update and activate)
The audio player should be redesigned to make it more visible and easier to use. It should be clearly recognizable when users open a statue’s information page.
The player should include familiar controls, such as:
Play and pause
Progress bar
Current playback time
Total audio duration
Volume control, where supported
The audio player should retrieve and play the correct audio file from the backend based on the language selected by the user.
Automated Calls
The app will keep using GPS for automated calls.
User can also start the audio player from the statue’s information page.
Listen to the relevant audio using the visible audio player.
The user must manually select the statue or location. The app should not automatically detect the user’s position or start an audio file automatically.
Audio Language (update and activate)
The audio player should follow the language selected by the user.
The default language will be English. If the user selects Dutch, the audio player should retrieve and play the Dutch audio file from the backend.
The selected language must apply consistently to:
Statue information
Buttons
Menus
Notifications
Audio-player controls
Audio content
If an audio file is not available in the selected language, the app should display a clear message or use the default English audio, depending on the agreed product requirements.
NB - we want to make sure that it is possible to dublicate the app in the account for a new project and therefore, we want this done to start with, to solve any issues there may be.
Payment 3 milestones
1st 40% start
2nd 40% upload works
3rd 20% check 14 days
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.