Build a polished Android-installable and responsive web app called “Atomic Habits Companion.” The entire user interface and all built-in content must be in English only. The app is for English learners and readers who want a guided, bite-size learning experience based on James Clear’s Atomic Habits. Use only original, concise paraphrases and educational explanations of the book’s ideas; do not reproduce or present substantial copyrighted passages from the book. Include a clear note that the app is an unofficial learning companion. Core experience: 1. Home / progress dashboard: show the learner’s current progress, completed lessons, percentage, streak or study days, vocabulary progress, and a prominent “Continue learning” action. Include a progress chart that updates from actual completion data. 2. Bite-size lesson flow: organize the experience into themed sections inspired by the book’s major concepts, such as identity-based habits, the habit loop, the Four Laws, environment design, making habits obvious/easy/attractive/satisfying, breaking bad habits, and long-term consistency. Create short original explanations, practical examples, and one or more reflection or comprehension questions per lesson. Let users mark lessons complete and revisit them. 3. Questions and answers: support multiple-choice and short written reflection questions. Save answers locally, show thoughtful feedback for objective questions, and allow users to edit their reflections later. 4. Vocabulary practice: extract or present selected advanced English words and phrases from the app’s original lesson content. For each item show a concise definition, a synonym, an example sentence, and optional practice such as matching, multiple choice, or fill-in-the-blank. Track learned and review items locally. 5. Word selection menu: when a user selects a word or phrase in lesson content, open a compact dropdown/context menu with “Look up” and “Highlight.” “Look up” should show a small vocabulary panel with a short explanation and synonym, using the app’s built-in vocabulary data and graceful fallback wording when an item is not in the built-in list. “Highlight” should activate the highlighting behavior and apply it to the selected text where supported. 6. Annotation tools: keep a small pen icon visible in the top-left area of the reading/lesson screen. Keep a Save button visible in the top-right area. Add a sticky-note button beside the pen icon. The pen tool should allow freehand writing over the lesson surface; the highlighter should allow translucent highlighting; the eraser should remove pen strokes or highlights. Provide 12 pastel color choices: green, pistachio green, azure, yellow, pink, dusty pink, iris, lilac, muted orange, muted red, black, and white. Use clear tool states and accessible labels. Annotations should be associated with the relevant lesson and persist locally. 7. Sticky notes: users can create a note attached to the current lesson or location. Each note supports typed text and optional freehand pen writing. Users can edit, move if practical, delete, and revisit notes. Clearly distinguish sticky notes from permanent lesson content. 8. Saving and persistence: include an explicit Save button available in the top-right corner of the main reading experience, plus sensible autosave. Save progress, answers, vocabulary status, annotations, colors, notes, and preferences entirely on the user’s device so they remain after closing and reopening. Include a simple local backup/export and restore option if feasible, without requiring accounts or a server. Do not add login, cloud sync, payments, chat, push notifications, or online leaderboards. Visual direction: Use a refined, warm editorial aesthetic inspired by the visual mood of Atomic Habits: warm cream and warm white surfaces, restrained shiny gold accents, dark readable text, subtle geometric shapes and circles, generous whitespace, and elegant but highly usable typography. Avoid an ugly, generic, or boring design. Use tasteful cards, progress rings/bars, gold dividers, soft shadows, and calm pastel annotation controls. Keep the interface focused and not visually cluttered. Add a settings/help area explaining the tools and the unofficial nature of the companion. Responsive and accessibility requirements: the layout must be mobile-first and responsive, designed first for narrow screens and then expanding to desktop. It must work from 360px width through full desktop width without breaking or horizontal scrolling. Do not use fixed pixel widths or fixed heights for text-containing sections; use flexible flex/grid layouts, percentages, and relative units. Make buttons and all touch targets at least 44x44px with adequate spacing. No feature may depend only on hover. Respect safe-area insets so the bottom navigation and device notches do not cover content. Include the standard meta viewport tag. On wide screens, use a centered readable content column with a supporting sidebar or two-column layout rather than stretching one narrow column across the whole screen. Ensure keyboard access, visible focus states, readable contrast, and accessible labels for drawing tools and controls. Keep the app entirely in English, including empty states, menus, tooltips, instructions, and error messages.










