A mobile interface to the Registry of Standard Biological Parts, built to run on Google App Engine.
Python CSS HTML Shell
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.




mPartsRegistry is a simple interface to the Registry of Standard Biological Parts aimed at mobile smartphone browsers. It's built using the Parts Registry API, JQuery Mobile, BeautifulSoup and Google App Engine.

The goal is not to completely replicate the functionality of the Registry (at this stage the API would not allow that anyhow), but to provide simple mobile-friendly interface to quickly look up important data about a Biobrick(tm) part in a laboratory setting, where accessing a desktop computer if often less convenient. In this context, you generally know the part name (eg B0034) that is written on a tube, but would like to quickly lookup some details (for instance, the size of the part in base pairs).

mPartsRegistry provides a simple 'bookmarking' feature, where a list of favorite parts can be managed and stored on the device (via HTML5 localStorage).

mPartsRegistry is released under the MIT License.

Old screenshots of the jQTouch interface (it looks a little different now)

mPartsRegistry screenshot, search page

mPartsRegistry screenshot, GFP part page

QR code to http://mpartsregistry.appspot.com/#search


Development and installation

If you just want to browse mPartsRegistry on your Webkit-enabled smartphone, go to http://mpartsregistry.appspot.com where there is a working version ready to use.

If you want to further develop mPartsRegistry and create your own custom installation, you'll need a need the App Engine SDK and should follow the instructions on how to upload an app.

Before you upload, you will need to change the application: name of the app in src/app.yaml from mpartsregistry to whatever you set it to in the App Engine dashboard.

Two convenience scripts are provided - start-server.sh, for starting the local development server, and update-server.sh, which uploads the app to App Engine. These scripts need to be edited to reflect the path where you installed the App Engine SDK.


  • Subpart support
  • DNA feature support
  • Twin support