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.

• Receive digital credentials from standards compliant issuers via link or QR code
• Store credentials on their mobile device
• Keep credential access safe with strong encryption best practices
• Create and share a presentation that collates any number of credentials in their wallet
• Backup and restore their wallet

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:

• Java
• nvm or asdf
• yarn or npm
• Node.js
• Cocoapods (use brew, not gem, to install)
• XCode
• Android Studio

See Installing on Linux on setting up the project on Linux.

1. Clone this repository or git pull
2. In root of project, run npm install to install the React Native dependencies.
   • (Optionally, if you use the asdf version manager run asdf install to install - more info in asdf section below)
3. Run npm run prebuild:ios and npm run prebuild:android to set up the ios and android folders. This step uses Expo prebuild.

• Run asdf install to install the proper versions of the technologies used listed in the .tool-versions file
  • If you need to install anything, run asdf plugin add [plugin-name] to add it to your local machine
  • Here is a link if you need it to the asdf installation documentation (homebrew is the easiest)

1. Run yarn start in one terminal
2. In another terminal run yarn android

• When running on android, open Android Studio and make sure the device you want to run on is selected (whether that is an emulator or a real device).
• Note: You might need to hit the play button in Android Studio for it to fully register which device to set to be used from the command line.

3. In another terminal yarn yarn ios

This 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 also use eslint to catch common mistakes and formatting errors. Most editors should support dynamic linting support while editing. If your editor does not, you can manually lint by running npm run lint in the project root.

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.

  • iOS: For iOS, check your target value inside your Podfile
  • Android: For Android, check that the rootProject.name in your 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:

• Create a new React component for your credential type in app/components/CredentialCard/ - eg. app/components/CredentialCard/YourNewTypeCard.tsx
• Define addition styles in app/components/CredentialCard/YourNewTypeCard.styles.tsx
• Add a function to the credentialTypes 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 display
• note: the list will be scanned for the first function that returns a component and title, so it's important that the type check is specific and doesn't match any other types.

The 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.

1. Open Settings > Accessibility
2. Enable relevant features:
   • VoiceOver: Screen reader for blind and low-vision users
   • Voice Control: Navigate using voice commands
   • Switch Control: Use external switches for navigation
   • Zoom: Magnify screen content
   • Display & Text Size: Adjust text size, contrast, and reduce motion

1. Open Settings > Accessibility
2. Enable relevant features:
   • TalkBack: Screen reader service
   • Voice Access: Voice control navigation
   • Switch Access: External switch navigation
   • Magnification: Screen magnification
   • High contrast text and Large text: Visual accessibility options

• Screen Reader Support: All UI elements include proper labels and descriptions
• Keyboard Navigation: Full app functionality available via external keyboards
• High Contrast: Supports system-wide high contrast modes
• Large Text: Respects system font size preferences
• Voice Control: Compatible with voice navigation systems
• Reduced Motion: Honors system preferences for reduced animations

iOS Accessibility Testing:

1. Run app on iOS simulator
2. Open Xcode > Developer Tools > Accessibility Inspector
3. Select your simulator from the target dropdown
4. Use the inspection tool to verify accessibility labels and roles
5. Run audit to identify accessibility issues

Android Accessibility Testing:

1. Run app on Android emulator
2. Open Android Studio > Tools > Layout Inspector
3. Select your running app process
4. Inspect accessibility properties in the Properties panel
5. Enable TalkBack in emulator settings to test screen reader functionality

1. Screen Reader Testing:

   • iOS: Enable VoiceOver in Settings
   • Android: Enable TalkBack in Settings
   • Navigate through the app using swipe gestures

2. Keyboard Navigation:

   • Connect external keyboard
   • Use Tab/Shift+Tab to navigate
   • Ensure all interactive elements are reachable

3. Visual Testing:

   • Test with large text sizes (up to 200%)
   • Verify high contrast mode compatibility
   • Check color contrast ratios meet WCAG standards

When contributing to the project, ensure accessibility by:

• Adding accessibilityLabel to all interactive elements
• Using accessibilityHint for complex interactions
• Setting appropriate accessibilityRole values
• Testing with screen readers during development
• Maintaining minimum color contrast ratios (4.5:1 for normal text)

We 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 [email protected].

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.