Release notes

SupaGrasp 1.2.11: less hunting, more continuity

1.2.11 tightens how readings, practice formats, courses, notes, goals, billing, and shared links behave together on iPhone, iPad, and Android. Below is a plain-language tour of what you get in this build, without the usual app-store fluff.

Version 1.2.11Published

Small releases earn trust when nothing surprising happens: screens stay where you expect them, limits explain themselves, and you do not rebuild context every time you reopen the app. That is the thread through 1.2.11. The scope is broad because studying rarely stays inside one feature, but the aim is narrow: keep your attention on the work, not on the interface.

Students collaborating around laptops during an online learning session
Readings and drills stay in one thread so prompts and outputs reference the same files you attached.

Readings and drills in one thread

You attach what you are working from, steer with plain instructions, and ask for output shapes that match prep, not just a wall of text. The formats line up with how review actually happens: quick recall checks, option sets, spatial summaries, flow sketches, staged assignments, and layouts that respect slide decks when those are part of the source.

When a quota bites, you see it in context. Low balances, gated actions, and deck image caps surface next to the control that triggered them. The intent is simple: adjust the constraint, then continue without guessing why something refused to run.

Laptop on a desk with notes and coffee, workspace for focused coursework
Playlist-style courses mirror how people actually block time: ordered modules, visible progress, and space to resume.

Courses that remember your place

Enrollment keeps an ordered path with progress you can scan at a glance. Resume after a break without reconstructing where you stopped. When something deserves praise or looks off, lightweight rating and reporting hooks sit nearby instead of hiding five menus deep.

Notes, goals, and todos as one habit loop

Notes favor fast capture and calm editing, with a dashboard so older entries stay reachable. Goals split vague intentions into steps you can log. Todos carry the near-term obligations so today's tasks live beside longer arcs instead of in another silo.

Plans and credits that read at point of use

Pricing screens mirror what checkout shows so comparisons stay honest. Points appear beside spend so a paused action comes with a reason, not a mystery. Subscription tasks route through the flows Apple and Google expect, including browser sheets when policy demands them.

Accounts that fit different front doors

Mail and password remain central, with signup, inbox verification, recovery, and hardware-backed unlock where available. Alternate providers cover common entry paths so first launch does not bottleneck on a single method. Stricter gate screens spell out what unlocks after sign-in instead of leaving newcomers stranded.

Links that behave on the web and after install

Shared threads and course URLs assume imperfect conditions: copied links, viewers without the binary yet, small screens. Companion pages on supagrasp.com explain the handoff so previews and fallbacks line up with what store listings promise.

Team gathered around a laptop collaborating on a shared screen
Shared URLs should survive messy handoffs between browsers, chat threads, and freshly installed builds.

Install or pull the update

1.2.11 is available on the App Store for iPhone and iPad and on Google Play for supported Android hardware. Already onboard? Fetch the update from the store screen you normally use so fixes and polish ride along with this version number.

  1. Open the App Store or Google Play on your device.
  2. Locate SupaGrasp from search or your library of purchases.
  3. Choose Update if it is installed, or install if it is not.
  4. Sign in and reopen threads, playlists, and notebooks from the last saved state.

Something feels off? Reach through in-app support or the contact route on supagrasp.com. Useful reports name the device model, OS level, and the last tap before the failure. That detail closes loops faster than screenshots alone.