Week 1 of Google Summer of Code is officially complete! This week, the major focus was translating our core project concepts into a visual reality, centering our efforts on creating a comprehensive Figma UI design for the BLT Vanish web page alongside deep-dive architecture discussions.
Here is a breakdown of the major work completed this week and the blueprint for what comes next.
π¨ Major Focus: Visualizing BLT Vanish
A significant portion of this week was dedicated to designing the homepage UI and strategically mapping out how to represent the core features of the app to the user. The goal was to build a clean, intuitive, and modern layout that clearly communicates our privacy-first tools.
π Check out the initial design work here: BLT Vanish Figma UI Design
π Architectural & Core Feature Alignment
In parallel with the UI design, we finalized the foundational system architecture to support these features seamlessly across platforms.
π± Cross-Platform Delivery: We aligned on using Flutter to build a cross-platform application capable of deploying smoothly across iOS, Android, and Windows.
π Privacy-First Architecture: Data sovereignty is a core pillar of the project. The app will store data locally on the user's device. The absolute minimum amount of data will ever be sent to the web, and it will be handled strictly via secure, encrypted JSON files.
π₯ 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! π»π‘οΈ
Top comments (0)