Audit & Architecture
- Review the current Base44 build
- Map data, users, files and backend logic
- Review bugs and priority interface issues
- Assess Flutter versus React Native
- Create the private GitHub repository
- Create the shared Figma workspace
Strengthening the current platform and establishing a scalable, professionally managed technical foundation.
Frankenstein Creations proposes a focused Phase 1 technical partnership to refine Safeguard Overwatch, transition its production foundation beyond Base44, develop a professional native mobile application and introduce stronger design, quality assurance and development controls.
Technical Development PartnerFrankenstein Creations Visit our main websiteMeet Sentry, Safeguard Overwatch’s operational guide. In ten seconds, he introduces the three foundations of Month 1: interface refinement, native app deployment and a secure employee download portal.
“Month one refines the platform, launches the native app, and gives every employee a secure place to download it.”
Base44 helped accelerate the initial Safeguard Overwatch build and prove the operational concept. Phase 1 will begin transitioning the production platform to a technical foundation that gives the project stronger scalability, cleaner development control and greater long-term ownership.
The proposed production backend will use Google Firebase, allowing the platform to grow without remaining dependent on a closed application-building environment.
Base44 application
Architecture audit and controlled migration
Google Firebase and native mobile application
Frankenstein Creations will assess the existing data, users, workflows, files and application logic before creating a controlled migration plan. The objective is to move the production foundation to Google Firebase while protecting the working functionality already built.
Secure user access
Operational application data
Images, reports and documents
Protected backend logic
Operational notifications
Role-based data protection
Issue tracking and visibility
Controlled exports and procedures
The mobile application will be rebuilt or packaged using Flutter or React Native, with the final framework selected after the technical audit. The decision will consider the existing code, required integrations, offline operation, maintainability and the fastest reliable route to a production-ready application.
The project will be connected to a private GitHub repository so that development is no longer dependent on changes made inside one platform. This creates a controlled technical record of the Safeguard Overwatch product and gives the development team a safer way to improve, review and release the application.
GitHub provides source control, development history and code recovery, supported by separate Firebase data-export procedures.
Lizemari Franken / Phase 1
Lizemari will support the project with focused UI/UX improvements, interface consistency, user-flow reviews and experience-based quality assurance. Her role is not to redesign the complete platform unnecessarily, but to identify friction, improve priority screens and create a professional design foundation that development can follow.
View Lizemari’s PortfolioA dedicated Figma workspace will be created for Safeguard Overwatch. Michael, as the client and product partner, will receive full collaborative access to review screens, leave comments, suggest changes and help shape the platform around his operational experience and long-term vision.
The Figma workspace should become the shared visual source of truth between the client, designer and development team.
The immediate goal is to give Safeguard Overwatch a scalable backend, professional native-app direction, controlled development workflow and collaborative product-design process—without losing the operational knowledge and functionality already built.
This separate delivery record shows what has been implemented after the proposal was approved: employee app distribution, a current Android release and a structured Q/A channel for real operational feedback.

The live portal gives employees a clear, controlled route to install the latest Android application and review the current release.

Issues, questions and flow blockers can now be captured with category, contact and screenshot evidence for a more useful review cycle.
A current mobile release is available for employee installation.
A dedicated portal provides download access and recent release visibility.
Employees can submit a title, description, category, contact details and attachments.
Real reports identify defects, blocked steps and opportunities to improve the experience.
Q/A to release workflow
The Q/A channel turns operational feedback into an auditable development backlog, rather than leaving issues in calls, messages or memory.
Submit Q/A via the employee portalEmployee reports a question, bug or flow issue.
The team confirms impact, context and steps to reproduce.
Critical defects and high-value improvements enter the delivery backlog.
Resolved work is tested, released and communicated in the next update.
Review the first submitted Q/A reports, identify repeated navigation and form friction, resolve confirmed defects, and use the findings to prioritise the next UI/UX improvements and native release.