Course Progress in a Learning App: Resume Lessons Without Losing Work
Remembering a video position is not the same as completing a lesson. Make progress useful to learners, teachers and support.
Reliable course progress separates the place a learner stopped, the activities completed and the work that passed assessment. Save these records against the learner and a stable lesson identity, explain offline changes awaiting sync, and define how device conflicts and edited courses are handled. The next lesson should follow the published learning rules, not an unexplained percentage.
Estimate your app with a short brief
StartA learner should return to the lesson, not to a puzzle
Someone studies during a commute, practises in the evening and opens the course on a tablet at the weekend. “Continue learning” ought to be a small convenience. Instead, it sometimes opens an old lesson, forgets an uploaded exercise or insists that an already completed module is unfinished.
A progress bar cannot repair those problems. The app first needs a shared meaning of progress: what it remembers, what it counts and which decisions belong to a teacher. Then the visual summary can be helpful rather than decorative.
This guide focuses on that record and its consequences. The online-school app guide covers the wider product, including teaching operations and access. Here we will follow a fictional practical course through interruption, revision and device changes.
Separate remembering a place from completing a task
A playback position answers “where did I stop?” Completion answers “have I finished the required activity?” Assessment answers “has the work met the course requirement?” They can move independently.
A student may replay an earlier explanation after passing an assignment. That should move the listening position without removing the pass. Another student may watch the whole demonstration but still owe a practical exercise. The player reaching the end should not silently approve the work.
Moodle's activity completion documentation is a useful reference: activities can use different completion criteria. For your product, choose a rule for each activity and express it in ordinary language beside the task.
Decide what the progress percentage actually counts
“Four of six required activities complete” is more informative than an unexplained 67 percent. It tells the learner what is missing and allows support to reconstruct the calculation. Optional reading should not quietly change that denominator.
Avoid mixing minutes watched, submitted assignments and passed tests into one apparently precise number unless you can explain the weighting. A shorter required assessment can matter more than a long optional introduction. Equal screen space is not equal learning importance.
Use the percentage as a summary with an accessible text equivalent. Keep the underlying checklist available. A learner should not need to guess whether the missing portion is a video, a teacher response or a new lesson added yesterday.
Define the state before choosing its colour
For a practical course, the following is a proposed model, not a standard every school must follow. It keeps learner actions separate from teacher decisions and technical confirmation.
| Record | What it means | What it must not imply |
|---|---|---|
| Resume position | Last useful point to reopen | The topic is understood |
| Activity completed | Published completion rule met | Every assessment passed |
| Work submitted | An attempt was received | Teacher approval |
| Changes requested | The learner needs to revise | The whole course has reset |
| Work approved | An authorized reviewer accepted an attempt | A professional qualification unless separately supported |
| Saved on device | Change is stored locally | The server has confirmed it |
Keep labels consistent across the home screen, course outline, player and support view. If “done” means watched in one place and approved in another, the app will teach users to distrust both.
Make “continue” a deliberate destination
A sensible default is the last active unfinished activity, but it will not fit every course. If homework is awaiting review, the next useful action might be practice rather than reopening the submission form. If the learner deliberately revisits a completed video, that should not necessarily replace the main continuation point.
Define a few precedence rules and test them. Consider the last interrupted activity, the next available required task and a teacher-requested revision. When more than one choice is reasonable, show the options instead of making an invisible decision.
The button should say where it leads. “Continue: shaping the bowl” is clearer than a generic “Go”. For a first-time learner with no record, the onboarding journey should lead naturally to the first available activity rather than a wall of empty statistics.
Save often enough to survive ordinary interruptions
A lesson can stop because the app closes, a call arrives, the device sleeps or the connection drops. Saving only when someone taps a tiny back arrow is a fragile arrangement. Record a useful checkpoint during playback and when the app moves out of active use, within the capabilities of the chosen platform.
Do not send every second as a permanent learning event. The team needs a reasonable balance between recovery precision, battery use and network traffic. The last recoverable position matters more than a visually busy stream of analytics.
Give the player a small rewind on resume if that helps restore context, but let the learner control it. There is no universal correct interval. Test with the actual material: a short language drill and a long equipment demonstration need different pacing.
Have an app idea and want a sober next step?
Review your app ideaExplain what is saved offline and what is still pending
Downloading a lesson, watching it offline and synchronizing a completion record are separate capabilities. A downloaded video does not prove that an exercise can be submitted or assessed without a connection.
Moodle's offline guidance describes activity-specific limits. The lesson for a custom app is to publish its own boundary clearly. A learner should know whether work is saved only on this phone, queued for upload or confirmed by the school.
When a connection returns, retry safely and preserve the work if synchronization fails. Distinguish an attachment still uploading from an assignment already received. Our offline synchronization guide covers the broader conflict problem; progress needs the same care even when the data looks small.
Do not let an old phone undo newer learning
Imagine a learner completes an activity on a tablet, then an older phone reconnects with yesterday's record. Accepting the last arriving message as the newest truth can erase a genuine completion. Arrival order is not necessarily action order.
Use stable activity identifiers, record changes with enough context to reconcile them, and define ownership by record type. A teacher approval should not be overwritten by a playback update. Rewatching should not lower the greatest completed course milestone automatically.
Some conflicts need an explicit choice. Two different unfinished drafts might both be valuable; keeping both is safer than silently discarding one. Explain the recovery to the learner and make the history accessible to authorized support without exposing unrelated submissions.
Keep revision history for homework
“Submitted” should mean a particular attempt was received, with its attachments. If a teacher requests changes, retain that attempt and the feedback while the learner prepares a new one. Otherwise a later dispute becomes impossible to understand.
Link feedback to the relevant attempt and lesson version. If the student replaces a photograph, the teacher should know whether they are reviewing the old or new image. Make the current action clear: edit a draft, submit a revision or wait for review.
The school also needs a realistic review operation. An app that promises feedback but gives teachers no queue, ownership or reply history will disappoint learners regardless of how accurate the progress bar is.
Edit courses without moving the finish line silently
Lessons will change. A spelling correction is different from replacing the final assignment. Keep lesson identities stable where the activity is genuinely the same, and decide when a material change creates a new version.
For existing learners, explain whether newly added work is optional, required for a new track or part of the original completion requirement. Do not silently take away a finished course because someone inserted another introduction.
Moodle's course completion page also distinguishes completion reporting from access restriction. For your app, specify these separately: recording an outcome, unlocking the next activity and granting paid access are not one decision.
Test progress as a journey, then measure it honestly
Use a test learner and complete a small course across two devices. Interrupt a video, submit work, request a revision, lose the network, reconnect an old device and edit a lesson. Compare the outline, continuation button, teacher queue and support record after every change.
Check whether a learner can explain what remains without your help. A correct database with an incomprehensible screen still fails the product test. The analytics guide helps distinguish product events from dependable operational records; an analytics event alone should not award completion.
Track repeated resume failures, unresolved sync attempts and activities where learners seek clarification. Look at completion alongside the teaching goal, not as proof of mastery. The Absorb mobile help example is additional reading on communicating download and synchronization steps, not a promise about your implementation.
Bring one course outline, its completion rules and the difficult continuation cases to Appfyl through the project brief. Those decisions give the feature a clearer shape than “add gamification”.
Turn research into a launch plan
Appfyl can turn your idea into a practical roadmap, scope and first sprint plan.
Discuss your app roadmapKey takeaways
- Keep resume position, completion and assessment as separate records.
- Explain the denominator behind any progress percentage.
- Protect newer learning from offline and multi-device conflicts.
- Preserve attempts and make curriculum changes visible.
Useful links
Questions people ask
Only if that is the published rule for that activity. A practical assignment or assessed quiz needs its own result. Watching is evidence of playback, not automatic evidence of understanding.
Yes, where the app supports it. Show locally saved changes as pending until synchronized, and explain which activities still require a connection or teacher review.
The confirmed progress should follow the authorized account. Unsynchronized local work needs a separate recovery route; it should not be assumed to exist on the new device already.
Not automatically. Decide how the new curriculum applies to existing learners, preserve historical completion and clearly identify any new requirements.