π₯ Mapping the Core User Workflows
The homepage UI and backend architecture were optimized around two distinct user personas:
π The Proactive Tracker: A user who actively keeps track of malicious websites, reports threats, and wants to secure their personal data and information from external exploits.
π The Remediation Seeker: A user focused on data reclamationβspecifically looking to request the removal of specific information from third-party sites and reporting platforms for breaching their data.
π οΈ Core Tech Stack
π» Client Application: Flutter (iOS, Android, Windows)
β‘ Serverless/Edge Logic: Cloudflare Python Workers
π Data Transport: Encrypted JSON files for web-based interactions
β‘ The Next Step: Contracts & Scaffolding
With the UI foundation laid and the high-level architecture agreed upon, the next phase is all about turning these concepts into structured data contracts and initial application scaffolding:
π Security Blueprints: Drafting comprehensive security contract specifications to outline the formal structures for Security Alerts, Risk Assessments, and Remediation Actions.
βοΈ Validator Engines: Building worker contract validators and writing cross-language contract tests to ensure seamless data integrity between the edge and the application.
π Scoring Infrastructure: Setting up the foundational scoring service skeleton to handle core risk-assessment logic within the application.
π― Target Deliverable: A frozen Version 1 contract specification integrated with automated Continuous Integration (CI) contract tests.
The visual momentum is shifting into code. Looking forward to sharing next week's development milestones! π»π‘οΈ
GSoC2026 #OWASP #OpenSource #UIUX #Figma #Flutter #Cloudflare #SoftwareEngineering