Build the first version of a professional mobile-first web application called "ScamShield".
ScamShield is an AI-powered scam and fraud detection platform that helps users identify potentially fraudulent messages, screenshots, and website links.
IMPORTANT:
- Do NOT build the entire application yet.
- For this first stage, build only the frontend foundation and navigation.
- Do not connect any AI API yet.
- Do not add payment/subscription functionality yet.
- Do not create fake scam detection results.
- Keep the code clean, modular, responsive, and easy to extend later.
BRAND:
Name: ScamShield
Tagline: "Know before you trust."
Style: Modern, trustworthy, professional cybersecurity/fintech appearance.
Use a clean interface with strong readability and accessible contrast.
The design should feel like a serious security product, not a gaming app.
CREATE THESE SCREENS:
1. Landing/Home screen
- ScamShield logo/name
- Tagline: "Know before you trust."
- Short explanation:
"Check suspicious messages, screenshots, and links before you act."
- Primary button: "Check for a Scam"
- Secondary button: "How It Works"
- Professional security-focused visual design
2. Dashboard
Show three main checking options:
- Check a Message
- Check a Screenshot
- Check a Link
Also show:
- Recent Checks
- Protection Status
- Upgrade to Premium section
3. Check Message screen
- Large text input area
- Placeholder: "Paste a suspicious message here..."
- Button: "Analyze Message"
- For now, the button should NOT perform real AI analysis.
- Display a clear placeholder indicating that the analysis engine will be connected in a later development stage.
4. Check Screenshot screen
- Upload image button
- Drag-and-drop area where appropriate
- Preview uploaded image
- Button: "Analyze Screenshot"
- Do not implement OCR or AI yet.
5. Check Link screen
- URL input
- Button: "Check Link"
- Do not implement real URL analysis yet.
6. Results screen
Create the UI structure only.
It should eventually display:
- Risk level
- Risk score
- Warning indicators
- Explanation
- Recommended action
- Report Scam button
Do not generate fake analysis results.
7. Profile/Settings screen
Include:
- Account information
- Subscription status
- Privacy settings
- Notification settings
- Logout
NAVIGATION:
Create a simple mobile-friendly bottom navigation:
- Home
- Check
- History
- Profile
Also make the application responsive on desktop.
SECURITY AND PRIVACY:
- Do not expose API keys in frontend code.
- Do not collect unnecessary personal information.
- Do not claim that the application can guarantee that something is safe.
- The future system should use language such as "Low Risk", "Suspicious", or "High Risk" rather than guaranteeing that a message is or is not a scam.
TECHNICAL REQUIREMENTS:
- Use a clean component-based architecture.
- Keep frontend components reusable.
- Use proper loading, error, and empty states.
- Use accessible buttons, labels, and form controls.
- Make the interface polished enough for a real startup MVP.
- Do not add unnecessary features that were not requested.
At the end, make sure the application runs successfully and that all navigation links work.
No preview
Comments (0)
No comments yet. Be the first!
Sign in to leave a comment
Project Tasks
22 planning tasks
#1
Generate system requirement document
0m 59s0.2 cr used
Done
#2
Generate personas & user flows
0m 11s0.2 cr used
Done
#7
Create flow for Scam Checker
0m 10sCredits in parent
Done
#8
Create flow for Returning User Reviewing History
0m 10sCredits in parent
Done
#9
Landing/Home screen
0m 47sCredits in subtasks
Paused
#20
Landing/Home screen / Landing Header
1.6 cr needed
Paused
#21
Landing/Home screen / Landing Hero Instrument
1.6 cr needed
Paused
#22
Landing/Home screen / Landing How It Works
1.6 cr needed
Paused
#23
Landing/Home screen / Landing Start Check Cta
1.6 cr needed
Paused
#24
Landing/Home screen / Landing Footer
1.6 cr needed
Paused
#10
Login
Credits in subtasks
Paused
#11
Sign Up
Credits in subtasks
Paused
#12
Dashboard
Credits in subtasks
Paused
#13
Check
Credits in subtasks
Paused
#14
Check Message screen
Credits in subtasks
Paused
#15
Check Screenshot screen
Credits in subtasks
Paused
#16
Check Link screen
Credits in subtasks
Paused
#17
Results screen
Credits in subtasks
Paused
#18
History
Credits in subtasks
Paused
#19
Profile/Settings screen
Credits in subtasks
Paused
#5
Architecture
0.2 cr needed
Paused
#6
Workspace task plan
0.2 cr needed
Paused
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No comments yet. Be the first!