
Learner Credential Wallet is a cross-platform iOS and Android mobile application for storing and sharing digital learner credentials.
Install Learner Credential Wallet for your mobile!
The wallet is based on the learner credential wallet specification developed by the Digital Credentials Consortium. The learner credential wallet specification is based on the draft W3C Universal Wallet interoperability specification and the draft W3C Verifiable Credentials data model.
The app has been compiled for iOS and Android and allows users to add and share credentials, as well as manage the wallet.

This learner credential wallet includes the features and technical requirements ultimately enabling individuals to curate and present their learning and employment records to others — for example, as applicants to educational programs or to apply for jobs with employers—in an interoperable manner.
Developers are welcome to open issues and PR’s on this repository. Please refer to CONTRIBUTING.md for information on how to contribute to this project.
The Learner Credential Wallet is one project out of many at the Digital Credentials Consortium. The DCC sends out regular updates on all the software we produce. If you would like to sign up for our software-specific mailing list, you can do so by going here.
The archive of DCC software updates is hosted here.
Additionally, we hold a monthly Technical Office Hours meeting on the third Thursday of every month, from 9:30-10:30am EST. You can register for these office hours here.
Please note, being part of the OpenWallet Foundation, we expect all interactions to adhere to the Antitrust Policy and [Code of Conduct][code-of-conduct].
The Digital Credentials Consortium is working with a number of colleges and universities to pilot test the wallet.
If you encounter any issues, visit the Troubleshooting Page
Prerequisites:
See Installing on Linux on setting up the project on Linux.
git pullnpm install to install the React Native dependencies.
asdf version manager run asdf install to install - more info in asdf section below)npm run prebuild:ios and npm run prebuild:android to set up the ios and android folders. This step uses Expo prebuild.asdf install to install the proper versions of the technologies used listed in the .tool-versions file
asdf plugin add [plugin-name] to add it to your local machineyarn start in one terminalyarn androidyarn iosThis project uses TypeScript and React Native with Expo. It would be best to use an editor that can hook into the TypeScript language server (VSCode does this with Intellisense, Vim does it with CoC). We use Prettier for code formatting with the following configuration:
trailingComma: 'none'semi: falsesingleQuote: trueMost editors support Prettier integration for automatic formatting on save. You can manually format code by running npm run format or check formatting with npm run lint in the project root.
VS Code:
Other Editors: Refer to Prettier’s editor integration guide for setup instructions.
This project also uses environment variables, which are loaded and used in app.config.js. These values can be overridden, but development values should not be committed to the repository.
├── app
│ ├── assets ← Image assets
│ ├── components ← React components
│ ├── hooks ← This is where custom hooks are defined (usually wraps lib methods)
│ ├── init ← Logger and registry setup
│ ├── lib ← Location for utility methods
│ ├── mock ← Location for mock data, usually used for testing
│ ├── model ← Database access objects and connections
│ ├── navigation ← React Navigation structure
│ ├── screens ← Individual screen views
│ ├── store ← Redux and Redux Toolkit definitions
│ │ └── slices ← Redux Toolkit slices (add new Redux state here)
│ ├── styles ← All app style definitions
│ └── types ← General place for defining types (usually DCC types for Credential, Presentation, etc...)
├── android ← Auto-generated android build folder, can still be manually edited if needed
└── ios ← Same as android, except it also uses Cocoapods for dependency management
└── patches ← Patches created for software maintenance
└── test ← Where tests are kept, can run `npm run test` and `npm run coverage:open` for coverage stats
Overridable configuration is in app.config.js
Setting up your own storage server is strongly encouraged. This storage server takes the role of verifying credentials added to the LCW. The VERIFIER_INSTANCE_URL can be updated in app.config.js as mentioned in the Environment section above.
The bundle identifier for your customized project will need to be updated in ios and android directories for Apple and Google app stores, respectively, if deploying to production. The display name in app.config.js, as well names under the expo section will need to be checked before deploying to app stores.
android/settings.gradle is up-to-date.Instructions for issuing a credential are here.
A custom display can be created for different credentials, to do so:
app/components/CredentialCard/YourNewTypeCard.tsxapp/components/CredentialCard/YourNewTypeCard.styles.tsxcredentialTypes list defined in
app/components/CredentialCard/CredentialCard.tsx.
The function should return {component: YourNewCredentialCard, title: 'the title of the credential that should be used when listing it elsewhere'} or null if the credential isn’t the appropriate type for you custom displayThe Learner Credential Wallet is designed to be accessible to all users, including those with disabilities. We follow WCAG 2.1 AA guidelines and have conducted comprehensive accessibility testing.
iOS Accessibility Testing:
Android Accessibility Testing:
When contributing to the project, ensure accessibility by:
accessibilityLabel to all interactive elementsaccessibilityHint for complex interactionsaccessibilityRole valuesWe have conducted a Voluntary Product Accessibility Test, please review the Learner Credential Wallet Accessibility Conformance Report, December 2021
For more information on accessibility please visit the MIT Accessibilty page.
This Privacy Policy explains how Learner Credential Wallet collects, uses, and processes personal information about our learners.
We do not collect any personal information.
We may change this Privacy Policy from time to time. If we make any significant changes in the way we treat your personal information we will make this clear on our website or by contacting you directly.
The controller for your personal information is the Learner Credential Wallet project at MIT. We can be contacted at lcw-support@mit.edu.
Learner Credential Wallet Terms and Conditions of Use
Initial development was supported by the U.S. Department of Education (Contract Number: 91990020C0105). The opinions expressed herein do not necessarily represent the positions or policies of the U.S. Department of Education, and no official endorsement by the U.S. Department of Education should be inferred.
Initial development was also supported by the Massachusetts Institute of Technology. Continued development is supported by members of the Digital Credentials Consortium.
MIT License Copyright (c) 2024 Massachusetts Institute of Technology
All files located in external directories are externally maintained libraries used by this software which have their own licenses; we recommend you read them, as their terms may differ from the terms above.