Mobile & iPhone UseየMobile እና iPhone አጠቃቀም
How GTM’s main shell, learning tools, Interlinear and three Concordances actually restructure across the audited responsive breakpoints.
ይህ መመሪያ የGTM interfaceን በMobile እና iPhone ላይ እንዴት መጠቀም እንደሚቻል ያብራራል። Interlinear እና Concordances ከማያ ገጹ ስፋት ጋር ተስማምተው እንዲታዩ responsive አቀራረብ ይጠቀማሉ።
How the main GTM shell changes on smaller screensዋናው GTM shell በmobile ላይ እንዴት ይሰራል?
The main responsive breakpoints are implemented in CSS rather than by a separate mobile application.
| Width | Main behavior |
|---|---|
| ≤1100px | Desktop sidebar collapses to a narrow icon-oriented rail; module and Grammar chapter grids reduce columns. |
| ≤760px | The app shell becomes a single block. The sidebar becomes a horizontal, scrollable navigation row; nav text is restored; the St. Jerome topbar quote is hidden; content padding reduces; grids stack to one column; Grammar reading sidebar becomes non-sticky. |
Dashboard on mobileDashboard በMobile ላይ
- At ≤1050px the major dashboard grids become single-column sections.
- At ≤650px the stat grid and mini-assessment grid become one column.
- The welcome/continue layout stacks vertically and its action button moves below the text.
Vocabulary / NT Greek 310 on mobileVocabulary / NT Greek 310 በMobile ላይ
- Vocabulary search/filter grids reduce to two columns at ≤1000px and one column at ≤680px.
- Learning-word cards move from multiple columns to two, then one.
- The NT Greek 310 hero stacks at ≤760px; its stats remain in a compact two-column grid.
- Game answer options become one column at ≤620px.
Interlinear on mobileInterlinear በMobile ላይ
The teaching-cell grid becomes two columns at ≤620px and one column at ≤390px. Neighbor navigation buttons also reduce in size. This means word-level layers may require more vertical scrolling, but the same data remains available.
When studying on iPhone, read the complete Greek verse first, then scroll into word-level cells rather than trying to compare too many teaching layers side-by-side.
Lexical Concordance on mobileLexical Concordance በMobile ላይ
- At ≤1050px filters/results reduce to two columns.
- At ≤680px filters, scope cards and result rows stack to one column.
- Saved-search rows switch to vertical alignment.
- Token-occurrence links remain compact grids; expect vertical scrolling for long result sets.
- Mobile-focused CSS raises control heights and font sizes around ≤760px.
Grammatical Concordance on mobile Grammatical Concordance በMobile ላይ
The production Grammatical Concordance has its own responsive layout. Ordinary Lemma browsing now uses the server-precompiled PT1904 lemma index, so the browser does not need to reconstruct the full corpus before displaying the lemma view.
- Lemma mode: designed for fast startup from the precompiled 5,383-lemma index.
- Parsed Forms / Occurrences: deeper occurrence-level work can require additional corpus processing and should be allowed more time than ordinary Lemma browsing.
- Filters, scope controls and result areas reflow for narrow screens, but dense analytical tables may still require horizontal scrolling.
- Advanced consensus, registry, audit, source-comparison and QA work remains more efficient on a desktop display.
Exegetical Concordance on mobileExegetical Concordance በMobile ላይ
The Exegetical app has explicit mobile restructuring:
- At ≤1100px the three-column workspace collapses; rail navigation becomes horizontal and relations move below.
- At ≤650px the command/search area becomes sticky and one-column, with Book/Chapter/Verse selectors restored as a mobile grid.
- The Greek verse, relation cards and glosses receive larger mobile typography in later R33 visual-QA rules.
- Reader View intentionally de-emphasizes machine-discovery cards; Research Audit View retains full research cards.
Complex audit registries can still be horizontally wide, so Reader View is the preferred phone experience.
Courses, assignments and academic records on mobileኮርሶች፣ Assignments እና መዝገቦች በMobile ላይ
Course grids stack to one column at ≤760px. Assignment/admin detail grids reduce at ≤850px and become one column around ≤580px. Record-list rows also stack. Formal assessment questions are designed as a single-question view and therefore adapt naturally to narrow screens, but long explanations still require vertical scrolling.
Safari / iPhone practical guidanceSafari / iPhone ተግባራዊ መመሪያ
- If a new deployment looks unchanged, use a deliberate reload and reopen the target route rather than repeatedly resubmitting an old POST/error page.
- Do not use Back/Refresh on a page created by a sensitive POST if Safari warns that it may resubmit a form.
- For Interlinear browser speech, available voice quality is device/browser dependent; this does not affect NT310 fixed-recording policy.
- Dense static Concordance research tables may require landscape orientation or desktop for efficient review.
Mobile finalization checklistየMobile መጨረሻ ማረጋገጫ ዝርዝር
- □ Capture current iPhone screenshots of every learner-facing top-level application.
- □ Test the horizontal mobile navigation with all menu items, including Help.
- □ Test assessment answer/finish flows on iPhone Safari.
- □ Test Interlinear teaching cells at ≤390px.
- □ Test Lexical search/filter forms at ≤680px.
- □ Test Reader View and selected Research Audit panels in Exegetical Concordance.
- □ Identify any Grammatical/Exegetical table that is technically responsive but practically unusable on a phone, and say so explicitly.