Lernern trains and places people into jobs across India. Its learners use the app to take skill-based courses, attend online and onsite classes, sit exams and apply for jobs. They arrive in three different ways: self-registered candidates who sign up in the app, students enrolled through a partner skill centre, and trainees placed through a client organisation. Each learner sees only their own data, and a message about a class, exam or document takes them straight to it.
We built the app from scratch, published it on Google Play and run its releases, including the store-account setup; the store account itself is owned by Lernern. We have developed and maintained it for over three years, through about 20 releases. Lernern chose the stack (Ionic, Angular and Capacitor), which lets one codebase be packaged for Android and iOS; the app is available on Google Play for Android only. The app has no backend of its own: it calls the same Core API as the admin portal, and the learner's user type decides which data it reads. Course content comes from Gooru's embedded player, and push messages are delivered through OneSignal.
Self-registered candidates, skill-centre students and placed trainees all sign in the same way. The user type decides which data the app reads, so each learner sees their own courses and documents.
A push message or deep link opens the exact class, exam or document it is about. If the learner is signed out, the app holds the destination and opens it after sign-in.
We run the builds, store submission and releases for the Google Play account that Lernern owns, about 20 releases over three years, with a forced-update check so learners on an old build are prompted to update.
A mobile number and a one-time code that Android reads automatically, or email and password, or Google. A forgotten password is reset with a code sent by email.
Browse the course catalogue, apply, then follow My Course: progress, time spent, the current quiz and the next online class, with the content in the embedded Gooru player.
Online and onsite class details show the module, competencies, duration and the Zoom link, and a session reminder opens the class directly.
Exams are listed in the app, and each one shows the learner's shift assignment, admit card and marks. An exam notification opens the matching exam.
Browse jobs, apply, track applications and receive offer letters by email. Questions and complaints go through a queries list in the app.
On Android the app reads the one-time code from the text message, so the learner does not type it. Signing in is simpler and friendlier, with email and Google as fallbacks.
Gooru publishes new player versions to the CDN the app loads from, so learners get player updates without waiting for an app release.
A reminder or exam notification opens the class, exam or document it is about, even if the learner has to sign in first.
We run the builds, Google Play submission and releases, about 20 so far, with a forced-update prompt so learners are not left on an old build.
On Android the app reads the one-time code from the text message, so the learner does not type it and signing in is one step shorter. Email and password and Google sign-in remain as fallbacks.
Self-registered candidates, skill-centre students and placed trainees share one app and one sign-in. The user type decides which records the app reads, and usage is tagged by user type.
A push opens the exact class, exam or document it is about. If the learner is signed out, the app stores the destination and opens it once they have signed in, so the message is not lost to the login screen.
A single request interceptor attaches the learner's token to every call to the API. When the API answers 401, the same interceptor shows a session-expired prompt, so no individual screen has to handle it.
The app checks its version against the API and prompts the learner to update when a release is required. That matters across about 20 releases, when learners do not all update at the same time.
Course content, quizzes and progress come from Gooru's embedded player. Gooru builds the player and publishes new versions to the CDN the app loads it from, so player updates reach learners without an app release from us.
A learner app is judged by small moments: a sign-in that does not ask for a code to be typed, a notification that opens the class it was about, an expired session that says so instead of failing. This app was built from scratch and has been kept running for over three years, through about 20 releases, on a stack Lernern chose. It shares its API with the admin portal described in the combined LMS study, and because we also run its Google Play releases, what we build reaches learners and stays current.
A learner app we built, publish and maintain on Google Play, on a stack chosen by Lernern
Region-to-region AWS migration for a live surf forecasting and camera-streaming platform: 718 resources across 20 services and three accounts, cut over with minimal downtime.
Virtual desktops for a biotechnology company's contractors and BYOD staff: ten role-based AWS Workspaces images joined to the client's own Active Directory, built to their HIPAA and HITRUST obligations.
Moving HIPAA-regulated Python microservices off a managed PaaS onto AWS: three environments rebuilt as code on ECS Fargate, PHI isolated in its own account, and roughly 60% off the monthly run-rate.
Lernern is a skilling and placement provider in India. We designed, built and run its learner management system: a staff admin portal, a learner app for Android and iOS, and one NestJS API — about 740 endpoints — behind both.
Tell us what you are trying to build, fix or migrate. We will look at your architecture, your costs and your risks, and come back with a recommendation in writing — whether or not it turns into an engagement.