• Home
• Tools
  • App Studio (Web)
  • FHC (CLI)
  • Eclipse Plugin (IDE)
• Reference
  • Development
    • Fundamentals
      • Client Development
      • Cloud Development
    • SDKs
      • JavaScript SDK
        • Introduction
        • Initialization
        • Calling a cloud side function
      • iOS SDK
        • Introduction
        • Quickstart
        • Initialization
        • Calling a cloud side function
        • Authentication/authorization
      • Android SDK
        • Introduction
        • Quickstart
        • Initialization
        • Calling a cloud side function
        • Authentication/authorization
    • Testing
      • Client
      • Cloud
      • Continuous Integration
    • Tutorials
      • 5 Minute App
        • Using the App Studio
        • Using Git
      • FHC Labs
        • Create an App from Github
        • Building an Android App
        • Building an iOS App
      • App Labs
        • App Anatomy
        • Mapping and Geolocation
        • Mash Hash Cache
        • Multilingual Support
        • Device API Tester
        • Current Date and Time Cache
    • HOWTOs
      • Choose App Libraries
      • Debugging
      • Push Notification
    • Building
      • App Resources
      • Uploading using FHC
      • Android (.apk)
      • iOS (.app)
    • Deploying
      • iOS Deploy
      • Android Deploy
    • Submitting
      • iOS App Store
      • Google Play
    • Data Sync Framework
    • Security Keys Management
  • Account Management
    • User API Keys
      • User API Keys (App Studio)
      • User API Keys (FHC)
  • Administration
    • Users
    • Auth Policies
      • oAuth
        • oAuth - Google
      • FeedHenry
      • LDAP
    • Mobile App Mgmt
      • App Store
      • App Store Items
      • App Store Item Groups
      • App Store Audit Log
      • Devices
  • Mobile App Store
  • Manage Deployment Targets
  • Endpoint Security
  • App Event Notifications
  • Manage Environment Variables
• API
  • Apps
    • Client
      • Android SDK API
      • iOS SDK API
      • Javascript SDK API
        • $fh.init
        • $fh.act
        • $fh.auth
        • $fh.sync
        • $fh.hash
        • $fh.sec
      • Hybrid Client APIs
        • Overview
        • $fh.init
        • $fh.act
        • $fh.auth
        • $fh.sync
        • $fh.acc
        • $fh.audio
        • $fh.cam
        • $fh.contacts
        • $fh.data
        • $fh.env
        • $fh.file
        • $fh.handlers
        • $fh.geoip
        • $fh.geo
        • $fh.log
        • $fh.map
        • $fh.send
        • $fh.notify
        • $fh.ori
        • $fh.push
        • $fh.ready
        • $fh.web
        • $fh.webview
    • Cloud
      • APIs
        • $fh.cache
        • $fh.hash
        • $fh.sec
        • $fh.web
        • $fh.feed
        • $fh.log
        • $fh.parse
        • $fh.stringify
        • $fh.util
        • $fh.push
        • $fh.db
      • Integrations
  • Platform
    • API Keys
    • Administration
      • Users
      • Roles
      • Auth Policies
      • App Store
      • App Store Items
      • Devices
    • Mobile App Store
      • App Store API
      • App Store Items API
      • App Store Audit Log API
    • Deployment Target
    • Endpoint Security API
    • Event Logs API
    • Environment Variables API
• Videos

A lot of developers prefer to use Javascript libraries/frameworks to speed up their development work and improve quality of their codes. To make it easier for developers to work on our platform, we add a new function recently to allow developers to choose or change libraries with few clicks.

When a developer chooses to create an app from scratch, one of the steps is to ask the developer to choose libraries. The developer can choose as many libraries as the app needs. One thing to note is that if a library is selected for an app, the javascript files of the library will not be included as the files of the app. Instead, those javascript files will be included automatically during the delivery/building process. However, some of the libraries require resource files (for example, jQuery Mobile requires css and images). To allow developers to customize their apps, those resource files will be added as a part of the app so that developers can edit or change them later (But not for git-based apps). The css files will be referenced in the app's index file if there are any.

Developers can also change the libraires for the apps afterwards. By selecting "Manage -> Libraries", developers will be presented with a view to update the libraries for the app. (For any apps that are created before this function was introduced, jQuery 1.3.2 will be selected as it is included by default previously). This will give developers the opportunity to update libraries of existing apps. However, there are two things need to notice here:

1. If the app is updated to use a library that requires resources (jQuery for example), the resource files will be created automatically (not for git-based apps) but will NOT be referenced in the app's index file. You need to update the app's index file to reference the resource files (If required).
2. If the app is updated to not use a library that uses resources, the resources files will NOT be deleted, and the references in the app's index file will not be removed as well (If there is any). You need to delete the files or remove the references manually.

Currently, the libraries that are available includes iScroll (for scrolling div), jQuery (the most popular Javascript library), jQuery Mobile (a jQuery UI framework for mobiles), XUI (a light weight javascript library for smart phones). We will add more libraries for developers to choose in the future.