Rotary Connect Israel
Product Requirements Document — Rotary Connect Israel
Working Name: Rotary Connect Israel
Alternative names: Rotary Network, Rotary Connections, Rotary Link Israel
Platform: iOS, Android, Responsive Web
Languages: Hebrew + English
Primary Organization: Rotary Israel — District 2490
Document Version: 1.0
1. Product Vision
Rotary Connect Israel is a private professional and personal connection network for the Rotary community in Israel.
The purpose is simple:
Find the right person, through Rotary.
A member who needs access to a company, profession, area of expertise, organization, industry, geographic location, or specific role should be able to search the Rotary network and quickly identify the people who can help.
For example:
-
“Who works at Microsoft?”
-
“Who knows someone at Elbit?”
-
“Find a cardiologist in Haifa.”
-
“Who works in real estate in Tel Aviv?”
-
“I need someone involved in venture capital.”
-
“Who is a lawyer specializing in commercial law?”
-
“Who works in the Ministry of Education?”
-
“Find a member who works in cybersecurity.”
-
“Who is a CEO or senior manager in the food industry?”
-
“Does anyone in Rotary have a connection to Samsung Korea?”
The application transforms Rotary Israel from a list of members into a living network of relationships, expertise and opportunities.
It should strengthen one of Rotary’s most valuable assets:
the people inside the organization.
2. Core Product Principle
The application is not intended to become another Facebook or LinkedIn.
There should be:
-
no endless social feed;
-
no follower counts;
-
no likes;
-
no popularity rankings;
-
no unnecessary posting;
-
no advertising;
-
no clutter.
The application revolves around three actions:
SEARCH → DISCOVER → CONNECT
Everything else is secondary.
3. Target Community
The network consists of:
Primary members
Verified members of Rotary clubs in Israel.
Family network
Rotary members may invite:
Family members must always be visibly identified as connected to a Rotary member.
Example:
Dana Cohen
Marketing Director · Strauss Group
Family of David Cohen
Rotary Club Haifa
For privacy and safeguarding, users under 18 should not appear as searchable professional contacts or receive unsolicited contact requests. If Rotary wishes to associate minors with a family account, their information should remain private and non-searchable.
4. Product Goals
Primary goals
-
Increase the practical value of Rotary membership.
-
Make the professional power of the Rotary community visible.
-
Help members reach people and organizations through trusted connections.
-
Encourage members to help other members.
-
strengthen relationships across clubs.
-
Create meaningful connections between members who otherwise would never meet.
-
Give younger members an additional reason to join Rotary.
-
Connect different generations of Rotary families.
-
Build a continuously improving professional knowledge graph of Rotary Israel.
-
Strengthen the feeling:
“Being part of Rotary gives me access to a trusted network.”
5. Core User Story
A Rotary member needs something.
They open the app.
Instead of navigating menus, the first thing they see is:
“Who are you looking for?”
Search examples:
Cybersecurity
Microsoft
Real estate lawyer
CEO food industry
Doctor in Haifa
Venture Capital
Samsung Korea
The application immediately searches across:
Results are shown in seconds.
6. User Registration
Rotary member
Initial onboarding:
Step 1 — Identity
-
First name
-
Last name
-
Mobile number
-
Email
-
Profile photo
Step 2 — Rotary
Step 3 — Professional identity
-
Profession
-
Specialty
-
Employer
-
Position
-
Industry
-
City
-
Country
Step 4 — Expertise
Select tags describing what the person knows.
Example:
Real Estate
Construction
Finance
AI
Healthcare
Law
Cybersecurity
Education
Government
Hospitality
Manufacturing
Step 5 — How can I help?
This is a particularly important part of the product.
Prompt:
“What can Rotary members contact you about?”
Examples:
Users can choose multiple categories.
7. Mandatory Profile Tags
Each searchable member must provide at least:
| Field | Example |
| ----------- | ------------------- |
| Profession | Lawyer |
| Specialty | Corporate Law |
| Workplace | Herzog Fox & Neeman |
| Role | Partner |
| Industry | Legal Services |
| Location | Tel Aviv |
| Rotary Club | Rotary Haifa |
Recommended additional tags:
8. Search
Search is the heart of the product.
The search bar should understand both structured keywords and normal sentences.
Examples:
Hebrew
“מי עובד באינטל?”
“מחפש רופא שמתמחה בקרדיולוגיה”
“מישהו שמכיר את עולם המלונאות בקוריאה”
“עורך דין בתחום הנדל״ן בתל אביב”
English
“Who works at Intel?”
“Find someone in venture capital.”
“Lawyer specializing in real estate.”
“Someone who has connections in South Korea.”
9. Search Filters
Users can refine search results by:
-
Company
-
Profession
-
Specialty
-
Job title
-
Industry
-
City
-
Country
-
Rotary club
-
Rotary district
-
Member / spouse / family
-
Language
-
Seniority
-
Expertise
-
“Can help with”
-
Current employer
-
Previous employer
Filters should appear only when needed.
The default experience should remain extremely simple.
10. Smart Search
Future versions should support semantic search.
Instead of requiring exact terms:
Search:
“Someone who understands importing medical equipment”
could identify profiles tagged:
-
Medical Devices
-
Import
-
Healthcare
-
Regulation
-
Supply Chain
The user should not need to know how another person tagged their profile.
11. Search Results
Each result should be compact.
Example:
David Levi
VP Business Development
Elbit Systems
Aerospace · Defense · International Business
📍 Haifa
Rotary Haifa
Can help with:
International business · Technology · Introductions
[View profile]
Results should clearly explain:
Why this person matched
Example:
Matched: Elbit Systems · Business Development · Aerospace
This greatly improves user confidence in search results.
12. Profile Page
A profile should feel closer to an elegant digital business card than a social-media profile.
Header
Photo
David Levi
VP Business Development
Elbit Systems
Rotary Club Haifa
About
Short optional professional introduction.
Professional
Company
Elbit Systems
Position
VP Business Development
Industry
Aerospace & Technology
Expertise
International Business
Defense Technology
Business Development
Asia
Can Help With
Rotary
Rotary Club Haifa
Member since 2017
Past Club President
Languages
Hebrew · English
Contact
Rather than exposing all personal information automatically:
Request Contact
or
Message
Depending on the privacy setting selected by the member.
13. Connection Request
A user chooses:
Contact David
They select a reason:
Optional message:
“Hi David, I am looking for someone at Elbit regarding…”
The receiving member sees the context before deciding whether to respond.
14. “Can You Introduce Me?”
One of the most valuable functions.
A member may not personally be the desired contact but may be able to make an introduction.
Profile button:
Request an Introduction
Example:
“I’m trying to reach the Innovation Division at your company. Would you be comfortable introducing me?”
The member may:
Accept
Decline
Ask for more information
This makes Rotary's relationship network far more powerful than a normal directory.
15. Company Pages
Selecting a company such as:
Microsoft
could show:
3 Rotary Network Connections
David Cohen
Senior Director
Yael Levi
Product Manager
Ron Ben David
Family member · Software Engineer
The page could also show past employees if they voluntarily enable this.
16. Profession Pages
Example:
Lawyers
184 people
Categories:
-
Commercial
-
Corporate
-
Real Estate
-
Tax
-
Family
-
Intellectual Property
-
Employment
-
Litigation
This allows discovery even when the user does not know exactly whom to search for.
17. Network Discovery
Secondary screen:
Explore the Rotary Network
Sections could include:
Industries
Technology
Finance
Healthcare
Real Estate
Law
Manufacturing
Education
Government
Tourism
Expertise
AI
Cybersecurity
Investment
Marketing
Leadership
International Trade
Medicine
Locations
Tel Aviv
Haifa
Jerusalem
Beer Sheva
North
Center
South
But this should remain secondary to search.
18. Saved Contacts
Users may privately bookmark useful contacts.
Collections:
-
Business
-
Healthcare
-
Technology
-
Travel
-
Rotary
-
Personal
Bookmarks are private.
There should be no visible follower/following counts.
19. Recent Searches
Users can optionally access previous searches:
-
Venture Capital
-
Korea
-
Cybersecurity
-
Commercial lawyer
Sensitive search history should remain private to the user and be removable at any time.
20. Home Screen
The home screen should be exceptionally clean.
Header
Rotary Connect
Small profile avatar
Main area
How can the Rotary network help you?
Large search field:
🔍 Search people, companies or expertise
Suggested searches:
Lawyer
Healthcare
Technology
Investments
International Business
Below
Recently viewed
and optionally:
New to the network
No news feed.
No giant dashboard.
No overwhelming navigation.
21. Navigation
Maximum four main navigation items:
Search
Network
Saved
Me
On Hebrew:
חיפוש
הרשת
שמורים
אני
22. Hebrew + English
The application must be designed from day one for both:
Hebrew — RTL
and
English — LTR
Do not design the English interface first and simply mirror it later.
Both directions should be native components of the design system.
Users can change language instantly.
Profile tags should be searchable across languages.
Example:
A profile tagged:
Real Estate
should appear when searching:
נדל״ן
The taxonomy therefore requires bilingual canonical tags.
23. Design Philosophy
The product should feel:
Premium
Human
Calm
Trustworthy
Modern
Fast
Professional
It should NOT feel:
-
AI-generated;
-
like a generic SaaS dashboard;
-
like LinkedIn;
-
like Facebook;
-
like a government database;
-
like a Rotary website from 15 years ago.
24. Avoid “Classic AI Design”
Specifically avoid:
-
excessive gradients;
-
glowing purple/blue backgrounds;
-
glassmorphism everywhere;
-
huge rounded cards floating everywhere;
-
giant gradient hero sections;
-
meaningless AI illustrations;
-
excessive pills;
-
dozens of dashboard widgets;
-
excessive shadows;
-
overuse of icons;
-
fake statistics;
-
unnecessary animation;
-
text like “Unlock the power of connections.”
The design should rely on:
Think:
premium members' network + modern contacts app + high-end professional directory.
25. Rotary Visual Identity
The application should respect Rotary’s official identity rather than reinventing or modifying it.
Rotary’s official guidance requires official club/district branding to be used consistently, without modifying the Rotary logo or wheel.
Brand use
Use:
Rotary District 2490 / Rotary Israel official lockup
rather than creating a new variation of the Rotary wheel.
The Rotary wheel can appear selectively as a recognizable brand device, but should never overwhelm the interface.
26. Color System
The interface should primarily use:
Background
White / warm off-white
Text
Near-black / deep charcoal
Primary accent
Rotary Royal Blue
Secondary accent
Rotary Gold
Gold should be used sparingly:
-
active state;
-
important highlights;
-
verified Rotary symbol;
-
small details.
It should not become the main background color.
The resulting product should look sophisticated rather than ceremonial.
27. Typography
Rotary's current Brand Center identifies Frutiger as a primary licensed typeface and Open Sans / Arial as free primary alternatives.
For the application:
English
Open Sans or an approved Rotary-compatible digital typeface.
Hebrew
Use a highly readable modern Hebrew typeface with matching proportions.
Typography should do most of the visual work.
Headings should be strong but restrained.
Body copy should remain highly readable.
28. Photography
Use genuine member photography.
Avoid stock photography whenever possible.
Member photos should feel natural and professional rather than corporate headshots exclusively.
The emphasis should be:
Real people inside Rotary Israel.
29. Onboarding Experience
First launch:
Screen 1
Rotary Connect Israel
**Your Rotary network.
One search away.**
Continue
Screen 2
What do you do?
Company
Role
Profession
Screen 3
What do you know?
Select your areas of expertise.
Screen 4
How can you help other Rotary members?
Select areas where members are welcome to contact you.
Screen 5
Profile completed.
Welcome to the network.
Search Rotary
Onboarding should take approximately 2–3 minutes for a basic profile.
30. Verification
Trust is fundamental.
A user should not be able simply to claim Rotary membership.
Possible verification methods:
Rotary members
Match against Rotary Israel membership records.
Family member
Invitation from a verified Rotary member.
Their account displays:
Family of [member name]
The Rotary member may revoke the relationship if necessary.
31. Privacy
Privacy must be part of the architecture rather than an afterthought.
Each profile field can have visibility:
Rotary Network
My Club
Connections Only
Private
Phone number and personal email should not automatically be publicly exposed.
Users determine how other members reach them.
32. Privacy Mode
Example:
David allows:
✓ Name
✓ Company
✓ Role
✓ Expertise
✓ Club
but hides:
✕ Phone
✕ Email
Members therefore see:
Contact David
rather than his phone number.
33. Data Ownership
Users must be able to:
-
edit their profile;
-
remove optional data;
-
control contact visibility;
-
download their information where legally required;
-
deactivate their account;
-
request account deletion.
Administrative access should be limited and logged.
34. Anti-Spam Rules
The network should never become a sales database.
Rules should prohibit:
-
mass messaging;
-
scraping;
-
harvesting contact information;
-
automated sales outreach;
-
exporting the complete directory;
-
marketing lists;
-
unsolicited bulk promotions.
Rate limits should apply to new contact requests.
Repeated abuse can trigger:
Warning → Restriction → Suspension.
35. Search Privacy
The system should NOT tell another person:
“Menachem searched for you.”
Searches remain private.
A member only knows another user was interested when that person sends a contact or introduction request.
36. Admin Portal
Rotary Israel administrators require a separate web administration interface.
Functions:
Member Management
Taxonomy
Manage:
-
professions;
-
industries;
-
specialties;
-
expertise;
-
companies;
-
languages.
Clubs
-
add/edit club;
-
club leadership;
-
membership.
Reports
Aggregate statistics only where appropriate:
-
active users;
-
searches;
-
successful connections;
-
profile completeness;
-
clubs using the system.
37. Club Administration
Each club may nominate an administrator.
The administrator can:
They should not have unrestricted access to private profile data.
38. Notifications
Notifications should be purposeful.
Send notifications for:
-
New contact request
-
Introduction request
-
Request accepted
-
New message
-
Profile needs updating
Avoid meaningless engagement notifications.
No:
“You haven't opened Rotary Connect recently!”
unless Rotary specifically chooses to implement it.
39. Profile Freshness
Professional information becomes outdated.
Every 6–12 months:
Is your information still correct?
Microsoft
VP Sales
[Everything is correct]
[Update profile]
This keeps the directory reliable.
40. Search Ranking
Recommended ranking signals:
-
Exact company match
-
Exact expertise match
-
Exact profession/specialty match
-
Job title
-
“Can help with” match
-
Geographic relevance
-
Profile completeness
-
Recently verified information
Rotary seniority should not automatically determine ranking.
A new member should be equally discoverable when they are the most relevant person.
41. AI Usage
AI should exist behind the interface, not dominate its appearance.
Possible AI functionality:
Query understanding
“Someone that can help me import equipment from Germany.”
Bilingual search
Hebrew query against English profile.
Synonym matching
CEO → Chief Executive → מנכ״ל
Tag recommendations
A user enters:
“Partner at commercial law firm.”
Suggested expertise:
Commercial Law
M&A
Corporate Law
Search summarization
“12 people match your search. Three currently work in banking and two specialize in fintech.”
AI should improve retrieval while the interface itself remains quiet and conventional.
42. Connection Paths — Future Feature
Future versions could answer:
“How am I connected to this person?”
Example:
You
↓
Rotary Haifa — David Cohen
↓
works with
↓
Sarah Levi — Microsoft
This creates a Rotary relationship graph.
However, relationship paths must only use information members have explicitly agreed to share.
43. International Expansion
The architecture should be built so Israel can later connect to other Rotary districts.
Example:
User searches:
“Someone in Taiwan semiconductor industry”
Results:
Rotary Israel
3 results
Rotary Taiwan
18 results
This could eventually create a genuinely powerful international professional Rotary network.
Therefore the architecture should support:
-
District
-
Country
-
Zone
-
Club
as separate entities from the beginning.
44. MVP
The first production version should stay focused.
MVP Includes
-
Member registration
-
Rotary verification
-
Family invitations
-
Profile creation
-
Company
-
Profession
-
Specialty
-
Position
-
Expertise tags
-
“Can help with”
-
Search
-
Filters
-
Search results
-
Profiles
-
Contact requests
-
Introduction requests
-
Saved contacts
-
Hebrew
-
English
-
Privacy controls
-
Admin portal
Not MVP
Do not initially build:
-
Social feed
-
Groups
-
Events
-
Marketplace
-
Business advertising
-
Payments
-
Video
-
Articles
-
Job marketplace
These can distract from validating the main idea.
45. Phase 2
Once search and connections are successful:
Network Graph
See how members are connected.
Opportunities
Members can post:
“Looking for someone in…”
rather than advertising products.
Mentorship
“Available to mentor”
“Looking for mentor”
International Rotary Search
Connect participating districts.
Events
Find people attending a Rotary event.
QR Networking
At conferences:
Scan Rotary QR → immediately add person to saved contacts.
46. Potential Phase 3 — Rotary Business Network
A later version could include:
Professional Groups
Technology
Healthcare
Finance
Law
Real Estate
Tourism
Manufacturing
Members could meet online or physically around professional interests.
This should be introduced only after the core member-search network has strong adoption.
47. Success Metrics
Do not measure success using:
“Time spent in app.”
The objective is not addiction.
Better metrics:
Adoption
% of Rotary Israel members registered.
Target first year:
70%+
Profile completeness
Target:
80%+
Search success
Percentage of searches resulting in viewing a relevant profile.
Target:
70%+
Connection rate
Percentage of contact requests receiving a response.
Target:
60%+
Network value
Monthly number of successful introductions.
Club penetration
Percentage of Rotary clubs with at least 50% participation.
48. North Star Metric
The most important measure should be:
Successful Connections per Month
A Successful Connection occurs when:
-
Person A searches;
-
discovers Person B;
-
sends a request;
-
Person B accepts or responds.
This directly measures whether Rotary's network is creating real value.
49. Recommended Technology Architecture
Mobile
React Native / Flutter
One codebase for:
Web
React / Next.js
Backend
Node.js / TypeScript or equivalent modern backend.
Database
PostgreSQL
Search
MVP:
PostgreSQL full-text search
Scale:
Elasticsearch / OpenSearch
Authentication
Passwordless authentication:
Email OTP
SMS OTP
Optional future:
Passkeys
50. Core Data Model
User
-
user_id
-
first_name
-
last_name
-
email
-
phone
-
photo
-
language
-
account_type
RotaryMembership
-
user_id
-
club_id
-
member_since
-
rotary_role
-
verified
FamilyRelationship
-
rotary_member_id
-
family_user_id
-
relationship
-
verified
ProfessionalProfile
-
user_id
-
company_id
-
position
-
profession
-
specialty
-
industry
-
city
-
country
Expertise
-
expertise_id
-
name_he
-
name_en
UserExpertise
HelpCategory
ContactRequest
-
sender
-
receiver
-
reason
-
message
-
status
-
timestamp
51. Search Screen — Concept
┌──────────────────────────────────┐
ROTARY CONNECT
How can the network help you?
┌──────────────────────────────┐
│ 🔍 Search people, companies │
│ or expertise │
└──────────────────────────────┘
Try
Technology Healthcare
Finance Real Estate
Recently searched
Microsoft
South Korea
Commercial lawyer
Search Network Saved Me
The real interface should have even less visual clutter than this schematic.
52. Profile Concept
←
[PHOTO]
DAVID COHEN
VP Business Development
ELBIT SYSTEMS
Rotary Club Haifa
────────────────────────
Expertise
International Business
Technology
Aerospace
Asian Markets
────────────────────────
Can help with
Corporate introductions
International partnerships
Business development
────────────────────────
[ Contact David ]
[ Request Introduction ]
53. Key Emotional Experience
The desired reaction after using the app should be:
“I didn't realize how many incredible people we have inside Rotary.”
And eventually:
“Before looking elsewhere, I search Rotary.”
That behavior is more important than any individual feature.
54. Strategic Value to Rotary Israel
Rotary Connect should not be viewed simply as an IT project.
It can become part of Rotary Israel's membership value proposition.
Instead of explaining Rotary membership only through:
-
volunteering;
-
meetings;
-
lectures;
-
community projects;
Rotary can also say:
Join one of Israel's most trusted networks of professionals, entrepreneurs, executives and community leaders.
It creates a direct and understandable benefit from membership while preserving Rotary's culture of service.
The underlying principle remains:
Give first. Connect second. Benefit together.
55. Recommended Product Positioning
External / recruitment
A community of people who can make things happen.
Inside Rotary
Your Rotary network. One search away.
Hebrew
הקשרים של רוטרי. בחיפוש אחד.
Alternative:
מחפשים אדם. מוצאים קשר.
or:
כל רוטרי ישראל — בחיבור אחד.
56. Recommended Launch Strategy
Stage 1 — Founding Network
Invite approximately 100–200 highly connected members representing:
-
technology;
-
medicine;
-
finance;
-
law;
-
academia;
-
real estate;
-
manufacturing;
-
government;
-
entrepreneurship;
-
social sector.
Their profiles create immediate value.
Stage 2 — Club Ambassadors
One ambassador per Rotary club.
Goal:
80% profile completion within each participating club.
Stage 3 — National Launch
Launch at a major Rotary Israel event.
Rather than simply presenting the app, demonstrate real searches live:
“Who in Rotary works in cybersecurity?”
“Who knows the banking sector?”
“Who can help someone entering the Japanese market?”
The audience immediately understands the value.
57. Product Rule
Every new feature must pass one test:
“Does this make it easier for one Rotary member to find or help another?”
If the answer is no, the feature probably does not belong in the product.
58. Product Summary
Rotary Connect Israel is a private, verified, bilingual relationship and expertise network for Rotary Israel and its families.
It converts information that is currently fragmented across clubs, personal relationships, WhatsApp groups and individual knowledge into a searchable network.
The app should be extraordinarily easy to understand:
Search someone.
Discover who can help.
Make the connection.
And visually it should represent a new generation of Rotary:
professional but not corporate,
modern but not trendy,
minimal but not empty,
distinctly Rotary without looking old-fashioned.
Rotary Connect should feel less like a social network and more like having the entire Rotary Israel community in your contacts.
You are acting as a senior product designer, UX/UI designer, frontend architect, and design-system specialist.
Your task is to completely redesign the existing app I provide.
Before making changes, inspect the entire project carefully:
You are allowed to install, download, or use any skills, MCP tools, UI libraries, icon libraries, components, packages, or supporting tools you need in order to produce the best result.
If useful, install appropriate design/UI skills before beginning.
Do not simply improve the existing colors or spacing.
I want a meaningful redesign of the whole user experience.
Main Design Direction
The app should feel like a premium modern social network.
Think about the usability and polish of products such as:
Use these only as references for quality, interaction patterns, clarity, and polish.
DO NOT copy them.
The final product must have its own identity.
The design must NOT look like a typical AI-generated application.
Avoid:
-
Excessive gradients
-
Purple/blue AI-style gradients
-
Giant rounded cards everywhere
-
Random floating glass panels
-
Excessive glow effects
-
Generic AI dashboards
-
Huge hero sections inside an application
-
Decorative elements with no purpose
-
Too many cards
-
Everything centered
-
Overuse of pills
-
Excessive whitespace
-
Artificial-looking illustrations
-
Repetitive card grids
-
Generic SaaS dashboard layouts
I want something that feels like it was designed by a professional product-design team.
Product Personality
The experience should feel:
Modern
Premium
Professional
Social
Friendly
Fast
Minimal
Trustworthy
Human
Intuitive
The interface should encourage users to discover people, connect with them, search the network, and return frequently.
Social Network Feel
The app should visually and behaviorally feel like a real social network rather than a corporate database.
Design appropriate social patterns such as:
-
User profiles
-
Profile photo/avatar
-
Name
-
Professional title
-
Company
-
Specialty
-
Profession
-
Role
-
Location when relevant
-
Rotary club / organization information
-
Mutual connections or relevant network relationships where appropriate
-
Contact actions
-
Save/favorite
-
Connect/contact
-
Share profile
-
Search
-
Suggestions
-
Recently viewed people
-
Recommended contacts
-
Relevant people based on search
-
Professional tags
-
Clean profile cards
-
Mobile profile views
-
Search history when useful
The goal is for users to think:
"I need someone who works at this company / has this profession / knows this field."
Then they should be able to find the right person extremely quickly.
Search Experience
Search is one of the most important parts of the product.
Redesign search so it feels exceptionally simple.
Allow users to search naturally by things such as:
-
Person name
-
Company
-
Position
-
Profession
-
Specialty
-
Industry
-
Rotary club
-
City
-
Skills or expertise
Create intelligent filters without making the experience complicated.
On desktop, filters may appear beside or above results.
On mobile, filters should use a clean bottom sheet, modal, or another mobile-native pattern.
Search results should prioritize readability and fast scanning.
Home / Discovery Experience
Create a useful home screen rather than a generic dashboard.
It can include things such as:
Do not overload the home screen.
Every element should have a clear reason to exist.
Profiles
Redesign profiles to look like high-quality professional social-network profiles.
A profile should make it immediately clear:
Who is this person?
What do they do?
Where do they work?
How can they help?
What is their expertise?
How are they connected to the network?
How can I contact them?
Create a strong visual hierarchy.
Important information should appear before less important details.
Profiles must work beautifully on mobile.
Mobile First
This application must work exceptionally well on phones.
Do not create a desktop interface and simply shrink it.
Design the mobile experience intentionally.
Consider:
-
Bottom navigation
-
Thumb-friendly controls
-
Large enough touch targets
-
Mobile search
-
Filter bottom sheets
-
Sticky important actions
-
Profile navigation
-
Responsive typography
-
Compact information hierarchy
-
Smooth transitions between pages
-
Proper safe areas
-
Keyboard behavior
-
Forms that are easy to complete on a phone
The app should feel almost like a native mobile social-network application.
Test layouts around common phone widths including approximately:
375px
390px
430px
Also make sure tablet and desktop layouts look excellent.
Navigation
Review the existing information architecture and improve it if necessary.
Do not preserve poor navigation just because it already exists.
Create a navigation system appropriate for a social network.
Desktop might use:
or
- A restrained side navigation
Mobile should likely use a simple bottom navigation for the most important destinations.
Avoid having too many navigation items.
Visual System
Create a consistent professional design system.
Define and consistently use:
Do not use arbitrary values everywhere.
Use a consistent spacing scale.
Keep shadows subtle.
Use borders and spacing more often than heavy shadows.
Typography
Typography should feel polished and modern.
Use excellent readability.
Create clear hierarchy between:
Page titles
Section headings
Profile names
Professional titles
Metadata
Body copy
Labels
Navigation
Do not use unnecessarily enormous text.
Logo and Branding
Preserve the existing brand identity where possible.
Inspect the current logo.
Fix its dimensions, padding, proportions, alignment, and placement if needed so it looks professionally integrated into the application.
Do not stretch or distort the logo.
Make sure it works correctly in:
Desktop navigation
Mobile navigation
Login/onboarding
Small header placements
Hebrew + English
The application must support both Hebrew and English.
The layout needs proper:
LTR support
RTL support
Do not simply reverse everything automatically.
Check:
Navigation
Icons
Back arrows
Forms
Search
Cards
Profiles
Modals
Spacing
Text alignment
The Hebrew version should feel intentionally designed, not like an English interface that was flipped.
Forms and Onboarding
Redesign onboarding and profile setup to be simple.
Users may need to enter details such as:
Name
Profile photo
Profession
Specialty
Company
Position
Rotary club
Contact information
Other relevant professional details
Do not put everything into one enormous form.
Use progressive steps if that improves usability.
Give users clear progress and make editing their profile easy.
Interaction Design
Add subtle, purposeful interactions.
Examples:
Hover states
Pressed states
Focus states
Loading feedback
Skeletons
Smooth page transitions
Dropdown behavior
Mobile sheets
Search feedback
Save/favorite feedback
Do not add animation just for decoration.
Animations should be fast and subtle.
Accessibility
Maintain strong accessibility.
Make sure there is:
Good contrast
Keyboard navigation
Visible focus states
Proper labels
Semantic HTML
Usable touch targets
Readable typography
Code Quality
Do not just create static mockups.
Implement the redesigned interface properly inside the current project.
Reuse existing functionality where possible.
Refactor UI architecture where necessary.
Create reusable components.
Avoid duplicated UI code.
Keep components maintainable.
Do not unnecessarily break backend functionality.
Do not replace working logic unless needed.
If the project already uses a component library, evaluate whether it is appropriate.
If another library would significantly improve the result, you may install it.
Icons
Use a professional consistent icon set.
Do NOT use random emoji as interface icons.
Use something such as Lucide, Phosphor, Material Symbols, or another appropriate high-quality icon system.
Keep icon stroke/style consistent.
Images and Avatars
Treat profile photography as an important part of the social-network feel.
Use realistic avatar placeholders when actual images are unavailable.
Do not use strange AI-generated profile imagery.
Create graceful fallbacks using initials when no photograph exists.
Empty States
Design meaningful empty states.
For example:
No search results
No saved contacts
No recently viewed profiles
No profile photo
No suggestions yet
Tell the user what they can do next.
Responsive QA
After implementing the redesign, inspect every major page at:
Mobile
Tablet
Laptop
Large desktop
Specifically look for:
Overflow
Broken text
Misaligned elements
Bad spacing
Buttons wrapping incorrectly
Huge empty areas
Cards becoming too wide
Navigation issues
RTL problems
Logo sizing issues
Poor mobile forms
Fix these issues instead of stopping after the first implementation.
Important Working Method
Do not immediately start rewriting random components.
First:
-
Audit the existing application.
-
Identify the major UX/design problems.
-
Understand the most important user flows.
-
Decide on the new information architecture.
-
Define the design direction.
-
Define reusable design tokens/components.
-
Implement the redesign.
-
Review it visually.
-
Fix inconsistencies.
-
Test desktop and mobile.
-
Test both Hebrew RTL and English LTR.
-
Continue iterating until the application looks cohesive and production-quality.
Do not stop after producing one screen that looks good.
Apply the redesign consistently throughout the entire application.
Final Quality Standard
The final application should look like a real startup/product company spent serious time designing it.
It should feel immediately understandable even to a user opening it for the first time.
A user should be able to:
Open the application →
Search for a professional/contact →
Understand the results →
Open a profile →
Understand how that person can help →
Contact or save that person
with almost no learning curve.
Prioritize usability over decorative design.
Prioritize hierarchy over visual effects.
Prioritize consistency over novelty.
Prioritize mobile usability as much as desktop.
Do not ask me to approve every small design decision.
Use professional judgment, make the changes, inspect the result, and continue improving anything that still looks unfinished, generic, awkward, or AI-generated.
When finished, summarize:
-
What UX problems you found
-
What you redesigned
-
What major components you created or changed
-
What responsive/mobile improvements you made
-
What RTL/Hebrew improvements you made
-
What packages, skills, or libraries you installed
-
Any remaining technical issues that genuinely require backend/product decisions
Make a new login questionnaire and it will contain this
Step 1 - Personal details (name, date of birth (and calculate age over time from this) type of Rotary club and year of entry into the fellowship)
Step 2 - Employment history and education so that the user enters his work history for the last 5 years and in which year he worked for each
And also whether he was involved in a board or association or any social activity and hobbies
Step 3 - Is he married and ask there gender, age and employment history and education so that the user enters his work history for the last 5 years and in which year he worked for each
And also whether he was involved in a board or association or any social activity and hobbies
Step 4 - Family ask how many children and ask for each child what his age is and what his current situation is, i.e. does he study at which institution, does he work in what job, etc.
If the children are under 28, do not allow the information to be entered and a message will pop up about this.
And the details stage will also allow you to enter the names of users on social networks such as Facebook, Instagram and LinkedIn.
Make the entire site default to Hebrew with the option to switch to English.
Make the entire site Hebrew by default with the option to switch to English. On all pages of the site
the register page still in english and at the history of jobs add from date to date and job description
insted of type of club do club name and do all the Make a selection of all Rotary club names.
On the account login page, you will have the option to search for one person, and after the search is complete, a message will pop up stating that in order to do more searches, you must register with the site.
Add at the bottom of the page (footer) at every page
Menachem Getz, District Governor, Rotary Israel, 2027-2028
And highlight the option to create an account if there is none on the first page, and put the Rotary logo there as well, and add another name to the club if it is not found.
Even if you log in with a Google account, the user will still have to go through the questionnaire stage of the register page.
This project was built with Lovable.
Build with Lovable
Continue developing this project in the Lovable editor.
- Ship faster: describe what you want to build and Lovable handles the code.
- Stay in sync: every change made in Lovable is committed straight to this repository.
- Full ownership: this code is yours. Push to
main on GitHub and your changes sync back into Lovable, ready for your next prompt.
Development
Prefer working locally? You need Node.js and npm — install with nvm.
git clone <this-repository-url>
cd <repository-name>
npm i
npm run dev
