Branded Aspen LiDA

Please note that if your library already has developer accounts for other apps, those existing accounts should be used to release Library Branded LiDA.

Apple Developer Account - Annual fee is $99
To set up an Apple Developer Account, use this link and follow the instructions for Enrolling in the Apple Developer Program as an organization.

If you are a nonprofit, you may be able to get this fee waived.

Google Play Developer Account - One time fee is $25
To set up a Google Play Developer Account, follow steps 1-4 at this link making sure to follow instructions for an organization account under step 2 of step 4.

Please read the below guidelines carefully, as we will not be able to use graphics that don't adhere to these requirements.

Logo for the Splash/Loading Screen

• Image size: 512 x 512 px
• File format: Must be in PNG format at 72 dpi. Transparency is allowed.

Logo for the Login Screen

• Image size: 512 x 512 px
• File format: Must be in PNG format at 72 dpi. Transparency is allowed.

Logo for the App Icon

• Image size: 512 x 512 px
• File format: Must be in PNG format at 72 dpi. Transparency is allowed.
• We strongly discourage the use of text in this image, as it will either not be legible or may get cut off.
• Please click here to review additional guidelines for the Google Play store.

Google Featured Graphic

• Image size: 1024 x 500px
• File format: Must be in JPEG or 24-bit PNG (no transparency/alpha) format at 72 dpi.
• Please click here to review additional guidelines for the Google Play store.

Example from Helen Plum Library:

Example from Darien Library:

Example from Los Gatos Library:

Notifications Graphic

(For use with push notifications from the app)

• Image size: 96 x 96 px
• File format: Must be in PNG format at 72 dpi, 100% white graphic (i.e., only white: no other colors, gradients, shadows, etc.) on a transparent background. SVG exported to PNG works best.

Screenshots

Screenshots will be provided and set up as a part of the LiDA app configuration. Screenshots will be provided for both the phone and tablet version. See examples below.

Apple Store

Google Play

The following information must also be provided in order to build your app. Please read the below requirements carefully to make sure everything is included; we will not be able to build your app without all of the required text.

App Name

(less than 30 characters)

This is the name of your app in the app stores and how users will likely search for your app. IMPORTANT: if an app with your chosen name currently exists in the app stores, the old app will need to either be renamed or completely removed before ByWater will be able to publish your LiDA app with the desired name.

Short Description

(80 characters or less, sample text below)

"Discover more from your library!"

Long description

(4000 characters or less, sample text below)

"[your app name] allows you to explore your library on the go to find new books, movies, games, or your old favorites! Quickly search the entire catalog, including eContent, and place holds, check due dates and renew eligible titles."

Support Email Address

This is a single email address provided in the app for support. This email is typically a library email and if the library cannot resolve an app issue they would put in a ticket with ByWater.

App testing account

Please provide a barcode and PIN to be used for ongoing testing in LiDA. Please be aware that the name on the account will appear in screenshots in the app stores.

Keywords

(100 characters or less)

The Apple App store requires you to supply keywords to assist users in finding the app.

Privacy Policy

You can use LiDA's default privacy policy or link to your own. If linking to your own, you'll need to provide the URL to your LiDA privacy policy. Your privacy policy should at a minimum include the information from LiDA's default privacy policy. 

Support Website and Phone Number
In addition to the support email address, you can provide a support website and phone number.

Video
If your library creates a video demonstrating how the app works, we can upload that to the app stores.

Q: Does the app name need to be the same in both app stores?

A: There are cases when libraries have had multiple past apps. We do need to use the same name for both iOS and Android. Libraries will need to reach out to those vendors and/or remove those other old apps from their accounts.

Q: What happens if a library has an existing app with the name they want to use for Aspen LiDA?

A: This name cannot be the same as any other app in the app store but can be changed later. We can suggest something like adding/dropping a word like ‘Public’ or ‘System’ or add a “+” in the new app as a work around. 

Q: Can a library change their app name once they decommission their old app?

A: Yes. 

Q: What is the process for changing the app name once the library decommissions other apps?

A: Make sure the old app(s) are deleted. Put in a ticket to request the change and we will try and park the name asap. We will need to coordinate the update with a release.

Q: What is the order of operations for library deleting their old app and us launching the new app of the same name?

A: Our LiDA developer prefers that library staff delete their old apps from the stores before we park on the name, so if someone at the library can delete the inactive app on the app store accounts, then we can begin parking on that name ASAP. We can coordinate this so that the name does not get taken.

Removing the app from the app store is the same as deleting it. In ios, it will disappear from the Apps tab: https://appstoreconnect.apple.com/apps. A splash screen will display, “No Apps. You haven’t added any apps yet. To get started, click Add Apps.” It may still appear under All Statuses > Removed Apps as a log of previous apps (that is fine!).

Q: If the library is using a temporary name, should we tell patrons and staff?

A: We generally don't recommend any kind of launch, even a soft launch, with an app name that the library doesn't really want to use in production. Ideally, we would only temporarily be using these names for beta apps in an internal test period.

Once the library is live on LiDA, they may receive notifications from the app store(s) or need to complete required steps in relation to keeping the app live and the account active.

This is not an exhaustive list and ByWater/LiDA Support has limited control over what types of requirements the app stores may roll out at any given time.

Library Will Need to Respond:

• Developer identity verification - If app stores update their requirements for documentation and verification of account holder, libraries must work with the app store(s) to complete these requirements.
• New Developer Agreements - If app stores update their requirements for development agreements, libraries must work with the app store(s) to sign the agreements in order to keep the app active and up to date.
  • Apple Store agreements are here: https://appstoreconnect.apple.com/agreements

ByWater/LiDA Support Team Will Handle:

• iOS Distribution Certificate - The ByWater Team handles these and they will be renewed automatically
• Builds & Releases - The ByWater Team will be taking care of any notifications related to builds and releases being flagged or denied

These settings can be found in Aspen Administration > Aspen LiDA > Branded App Settings.

Here you will find information on the logos uploaded to your branded app as well as areas to customize the Privacy Policy information.

Your branded Aspen LiDA app will be preloaded with a Privacy Policy.

By default, the contact information is the Location marked "is Main Branch" in Aspen Administration > Primary Configuration > Locations. If no location is marked "is Main Branch", then it will be the first location code alphabetically.

You can change the default contact information by going to Aspen Administration > Aspen LiDA > Branded App Settings > Privacy Policy Information.

• Address
• Phone Number
• Email

Go to Aspen Administration > Aspen LiDA > Branded App Settings > Show favicons for each library at login to have each of the library system favicons (uploaded in their individual Theme settings) display on the search screen.

In Aspen Administration > Aspen LiDA > Branded App Settings > Use User Home Location When Logging In will be checked by default. This is recommended.

This allows users of the Branded LiDA app to skip selecting a location if they are a multi-branch system/consortium. 

Note: The library's custom logo will be in the place of the Aspen LiDA logo below.

When users launch the app, they will see this screen.

Aspen can determine the user's home library upon login without the user needing to select their library.

If libraries uncheck Use User Home Location When Logging In and have multiple locations, when users launch the app, they will see this screen.

Note: The library's custom logo will be in the place of the Aspen LiDA logo below.

The user will have an extra step of selecting their home library.

Branded LiDA only uses Primary, Secondary and Tertiary colors from the theme.

In some cases, libraries might have colors that are too light/bright to display nicely in LiDA. In this case, you can create a separate theme ({Library Name} - LiDA) within Aspen Discovery. Do not apply it to any libraries or locations. Simply, put in a ticket or indicate during the implementation process the ID of the new LiDA theme you'd like to use.