As a new customer of SeeClickFix, you may have an existing service request/311 mobile app published in the stores and are replacing it with a marketplace mobile app from SeeClickFix. If this is the case, two options are available to you for this transition.

Important Note

This article does not apply to SeeClickFix customers in the following scenarios:

• You use only the SeeClickFix container app and/or do not have your developer accounts within one or both App Store for iOS and Google Play Store.
• You upgrade to the SeeClickFix marketplace app option but is not replacing an existing request/311 app. You may have other mobile apps within your store accounts unrelated to request/311 services.

Option One – Remove the Existing Apps

First, you can choose to simply remove the existing mobile apps from the Apple and Google Play app stores.

1. SeeClickFix can publish a fully new marketplace app on your behalf. You'll need to select a new name for the mobile app (this is advisable anyway as having the same name could confuse residents).
2. You will need to publish an iOS app.
   • You should be sure to contact your prior app provider and request the apps to be removed from stores.  

Option Two – Write Over the Existing Apps

SeeClickFix can write over the existing mobile apps if given proper access.

Instructions for iOS

If you are already set up as the developer (publisher) of the app for the App Store then this is relatively simple. Most organizations will be the direct publisher of the app as this was a requirement Apple put into place in 2017.

1. You need to provide SeeClickFix access at the Admin role level on their Apple Developer account. 
2. Once SeeClickFix has been given access, our engineering team can "write over" the existing app.
3. Residents will then need to do an update to the app.  

Please note, if your current app is also available for iPad apps, there may be challenges in updating the app to the SeeClickFix app, which does not have an iPad version. At this time, SeeClickFix has successfully updated apps with this challenge, but this may change per Apple’s review and requirements. 

If you are not the developer of the app for the App Store, then the first step is to contact your prior provider and see if they will transfer the app to the customer’s Apple Developer account.

Instructions for Google Play

The first step for Google is to determine if the customer is already the Developer of the Google Play app. 

If you are not the developer of the app for the Google Play Store, then the first step is to contact your prior provider and see if they will transfer the app to the customer’s Developer account.

• How to set up a Google Play Developer Account and transfer an app between accounts. 
• This is often not able to be done because either the original developer does not want to transfer the app or the original developer cannot find the required information, such as their account transaction ID. The original developer also needs to be able to provide the Signing Key for the app to the customer.  

If you are not able to achieve the transfer of the app, then SeeClickFix can publish a new app on your behalf. For simplicity and easier communication, we recommend removing both iOS and Android apps and publishing brand new apps with new names on the stores.    

If you are the original developer or successfully have the app transferred to your developer account, then the next step is to give SeeClickFix access.

• Follow the instructions to add mobile@seeclickfix.com as an Admin to the Google Developer account.
• After adding SeeClickFix 311 CRM to the account, you will need to provide the original Signing Key for the app (which needs to have come from the original publisher of the app). The signing key should not be sent over email without being in an encrypted file.  
• Once SeeClickFix 311 CRM has been given access and the necessary information, our engineering team can "write over" the existing app. Residents would then just need to do an update to the app.