Presentation

[Virtual Presenter] Flojas Symptom Journal Welcome Flojas Symptom Journal is a private personal journal for logging symptoms, spotting patterns, and remembering what happened when. It is not a medical device, diagnosis tool, triage tool, or substitute for professional care. Available in 27 languages Not medical advice Data stays under user control Welcome. Welcome to Flojas Symptom Journal. This is a private personal journal designed to help a user record symptoms, remember timing, and review their own patterns. It is available in 27 different languages. It is not a medical device, not a diagnosis tool, not a triage tool, and not a substitute for professional care. The app is built to be useful, careful, and patient centered from the first screen..

[Audio] A warm first impression before setup The user meets Flojas first, then moves through the required agreement and restore option without confusion. Friendly intro Clear agreement Restore path Onboarding. The first use flow should feel warm, clear, and responsible. The user meets Flojas as a simple place to log symptoms, spot patterns, and remember what happened when. Then the app moves into the agreement and restore path so the setup feels guided rather than abrupt..

[Audio] Consent is visible and deliberate The disclosure is readable, scrollable, and accepted intentionally before the app continues. Readable disclosure Active acceptance Agreement. The legal agreement is not hidden. The user can read the disclosure, privacy, and disclaimer content, scroll through it, and actively accept it. This keeps the first run experience transparent and responsible before any symptom data is entered..

[Audio] Reinstalling users can restore continuity If a prior C-S-V exists, the user can import during setup or later from Export and Import. Import after reinstall Export/import remains inside app Continuity. A reinstalling user can bring their journal back by importing the C-S-V they previously exported. If this is the first installation, they can ignore the message and continue. The same export and import pathway remains available inside the app, so continuity is explained at the right moment and preserved later..

[Audio] 27 languages Available in 27 languages Highlighted examples 中文 Mandarin Chinese Español Spanish Flojas supports a broad language set after the legal agreement, including Mandarin Chinese, Spanish, and Hindi. हिन्दी Hindi English Arabic Bengali Dutch French Chinese German Hindi Indonesian Mandarin Chinese / 中文 Japanese Korean Italian Malay Persian Polish Spanish / Español Portuguese Russian Spanish Telugu Swahili Tamil Hindi / हिन्दी Thai Turkish Ukrainian Urdu Vietnamese Traditional Chinese Language. Flojas is available in 27 different languages after the legal agreement. This slide highlights Mandarin Chinese, Spanish, and Hindi as examples, while the full language grid reinforces that the app is designed for a broad multilingual audience. The user can choose language during setup and adjust it later in Settings..

[Audio] Quick logging can start outside the app The widget gives a shortcut back to the same local journal so entries can still feed history and analysis. Launcher shortcut Same local data Widget. The widget gives the user a faster path to logging without opening the full app flow first. It connects to the same local journal data used by the app, so quick entries can still appear in history, analysis, reports, and exports..

[Audio] Logging starts with the next likely entry Prior logs can pre fill the form, reducing repeated taps while leaving every field editable. Pre filled for convenience Review before saving Logging. The home screen is one of the most important screens in the app. When prior logs exist, Flojas can pre fill the next likely entry so the user can review, edit, and save quickly. This reduces friction while keeping control in the user’s hands..

[Audio] Saving is visible and reversible The save flow confirms the entry, allows undo, and immediately appears in History. Save confirmation Undo available History updates Saving. The logging flow should make the user feel certain. The user reviews the entry, taps Save to Device, sees a confirmation with Undo and OK, and can verify the record in History. That short feedback loop is what makes frequent logging feel safe..

[Audio] No symptom days are meaningful data A quiet day is logged deliberately and kept separate from days where the user simply did not enter anything. Zero symptom is explicit Clean day logic Zero. A no symptom day is not the same as a missing day. Flojas treats it as deliberate information. If the user later logs a symptom before midnight, that no symptom entry can be removed so the day remains logically clean..

[Audio] History stays readable and correctable The user can review local records and remove incorrect entries without leaving the app. Local audit trail Delete mistakes History. History is the user’s local audit trail. It should be readable, searchable in practice, and correctable. When a user makes a mistake, they can delete the entry directly from history without feeling trapped by the record..

[Audio] Analysis begins with clear choices The user chooses symptom, body part, time frame, and no log handling before any chart is generated. Four required inputs No hidden assumptions Scope. The Analyze page asks the user to define the question before showing results. The required choices are symptom, body part or logged location, time frame, and how to treat days with no logs. This prevents hidden assumptions and makes the resulting graphs easier to trust..

[Audio] Analyze one symptom, several, or all The multi select symptom picker supports broad review and focused questions without showing irrelevant choices. All or selected symptoms Only logged options matter Selection. The symptom picker supports All, one symptom, or multiple symptoms. If All is selected, logged symptoms are selected together. If the user narrows the choice, the analysis follows that narrower scope. The goal is flexibility without clutter..

[Audio] Date ranges use plain language Common windows are easy to choose, with custom dates available when the user needs precision. Six month period included Custom range available Time. The time picker uses familiar language: today, this week, this month, this quarter, six months, this year, all, and custom dates. The six month period is especially useful because it gives enough history to see patterns without overwhelming the user..

[Audio] No log days are handled honestly The app asks whether missing days should count as zero before calculating results. User chooses the assumption Analyze becomes next step Math. A day with no log can mean no symptom, or it can mean the user did not enter anything. Flojas asks the user how to treat those days before analysis. Once all inputs are complete, the Analyze button becomes the next obvious action..

[Audio] Results open with action and summary Export options and a readable summary appear before the deeper graph stack. PDF, P-N-G--, C-S-V--, calendar Summary before detail Results. After the user taps Analyze, the app immediately becomes useful. Export options appear first, then a readable summary, and then the deeper graph stack. The user can export, understand the headline pattern, or scroll into detail depending on what they need..

[Audio] A readable summary comes before interpretation Trend, daily, weekly, monthly, and statistics are summarized in patient friendly language. Plain language summary Details below Summary. The summary card translates the selected analysis into plain language before asking the user to interpret charts. It summarizes trend, daily pattern, weekly pattern, monthly pattern, and statistics in one place. This is useful without sounding clinical or diagnostic..

[Audio] Intensity over time is the first graph story The trend graph shows the selected range, peak, average, and direction. Large graph focus Selected range only Trend. The Intensity Trend Graph is central to the app’s value. It answers a simple patient centered question: how has this symptom changed over the selected period? The graph shows the selected range, peak intensity, average intensity, and direction without pretending to explain the medical cause..

[Audio] Daily pattern is easy to read Time of day buckets replace cluttered dots and show when symptoms are strongest. Larger graph view Morning to overnight buckets Daily. The daily pattern graph is designed to be readable. Instead of a crowded scatterplot, it groups logs into time of day buckets such as morning, afternoon, evening, and overnight. That gives the user a practical answer: when during the day does this symptom tend to be strongest?.

[Audio] Weekly pattern stays inside the selected range The same analyzed dates are grouped into weekly buckets without separate anchors. Same range, new grouping Cleaner logic Weekly. Weekly pattern analysis uses the same date range selected at the top of the Analyze page. It does not ask for separate From and To anchors and does not project into unrelated dates. It simply groups the selected range into weekly buckets so the rhythm is easier to see..

[Audio] Monthly grouping compares calendar timing The view changes grouping only; the underlying analysis scope stays consistent. Calendar timing patterns Scope remains consistent Monthly. Monthly pattern analysis is another lens on the same selected data. It helps the user notice whether symptoms cluster around parts of a month. The logic remains clean because daily, weekly, and monthly views change grouping, not the underlying scope..

[Audio] Statistics add context without overreach The numbers summarize the user’s own logs while staying clearly patient centered. Average, range, counts No diagnosis language Stats. The statistics card adds useful context using the user’s own entries. It can show averages, range, counts, and related summaries, but it stays careful and patient centered. Flojas explains the journal data; it does not diagnose or triage..

[Audio] The full P-D-F report is comprehensive Identity, logo, summary, trend, patterns, stats, raw data, and disclaimer are included. Complete analysis export Useful for review PDF. The P-D-F report is the comprehensive export. It includes user identity and Flojas branding at the top, summary, trend, daily weekly and monthly pattern analysis, statistics, raw data for the selected item, and the disclaimer. It is designed to be useful while remaining clearly framed as a personal symptom journal..

[Audio] P-D-F report: multiple views in one export The P-D-F turns the selected analysis into a polished personal report, not just a screenshot. Full report view Summary and graph details Ready for review PDF. The P-D-F report is one of the strongest parts of Flojas. It converts the selected analysis into a polished personal report with identity, Flojas branding, summary, graphs, statistics, and raw entries. This slide shows that the export is more than a saved image; it is a structured report the user can keep for their own records or review later..

[Audio] P-D-F report: readable sections The report separates the top summary, trend and raw data, and the disclaimer footer so the user can scan it quickly. Top summary Trend plus raw logs Disclaimer footer PDF. The report is organized into sections the user can understand at a glance: identity and summary at the top, trend and raw data in the body, and the disclaimer at the bottom. The goal is to make the export informative while keeping it clearly patient centered and clearly framed as a personal journal, not medical advice..

[Audio] A focused visual can be exported cleanly PNG export captures a graph or visual report without sending the full data file. Presentation ready image Same analysis scope PNG. P-N-G export is for a focused visual: one graph, one report view, or one clean image the user can save or share. It follows the same analysis scope the user selected, so the export matches the view they were reviewing..

[Audio] C-S-V backup protects continuity All local data can be exported with an integrity code and imported later. Export before uninstall Do not edit the file CSV. The C-S-V export protects continuity. It exports all local logs so the user can reinstall or move devices and import later. The file includes an integrity code, and the user is told not to edit the file because changes may prevent a clean import..

[Audio] Calendar view turns logs into a visual journal Selected logs become a month at a glance record that is easier to scan. Visual journal page Same selected scope Calendar. The monthly calendar gives the user a familiar visual way to review entries. It makes clusters and quiet days easier to see without reading every raw log. Like the graphs, it stays tied to the selected analysis scope..

[Audio] Settings keep ownership visible Language, profile, retention, deletion, support, and developer details stay easy to find. Auto delete options Delete data without uninstalling Control. Settings are organized around user ownership. The user can update language and profile, choose retention and auto delete timing, delete local data without uninstalling, review accepted terms, and contact support. Important controls are visible without making the page feel crowded..

[Audio] Thank you Flojas Symptom Journal is a private personal journal. It is not medical advice, not a diagnosis, and not a substitute for professional care. Thank you from Flojas By teJai Technologies L-L-C Use for personal records only Thank you. Thank you from Flojas Symptom Journal by teJai Technologies L-L-C--. Flojas is a private symptom journal designed for personal records, fast logging, editable history, meaningful analysis, safe export, and availability in 27 different languages. It is not medical advice, not a diagnosis tool, not emergency guidance, and not a substitute for professional care..