Event Creation - Free Startup Idea Documentation

Event Creation Functionality

1. Request Location Permissions

Prompt the user to grant location permissions at the start of the Event Creation flow.
If permission is denied:
Display an error message explaining that location permissions are required to create an event.
Redirect the user back to the previous screen or keep them on the location permissions page until granted.

2. Event Discovery Integration

Begin Event Creation with Event Discovery to check for duplicates.
Outcomes from Event Discovery:
1.If Event Found:
Redirect Options:
To Dashboard if the user entered Event Creation directly.
To Image Upload if they were attempting to upload photos before joining an event.
2.If Event Not Found:
Proceed to Event Creation Component.

3. Map-Based Location Specification

Display a map starting with a view of nearby event centres, churches, mosques, educational establishments, and other relevant landmarks.
Use markers or pins to denote these points of interest (POIs).
Allow users to select an existing POI as the event location.
Users can also manually specify the event location by:
1.Dropping a Pin: Offers high precision with latitude/longitude coordinates.
2.Entering an Address: If available, the system resolves this to a geocode (latitude/longitude).
Address Validation:
Use reverse geocoding to generate a human-readable address from the map location.
Display the derived address to users for confirmation (e.g., “You selected XYZ Street, Lagos.”).
Let users manually adjust the displayed address if it seems incorrect or ambiguous.

4. Authorization-Based Rules for Event Location

Admin Users:
No location restrictions. Admins can create events anywhere.
Photographers:
Restrict event creation to their immediate locality.
Distance Constraint:
Define “locality” as a radius (e.g., 5 km) from the photographer’s detected location.
Notify the photographer if they attempt to create an event outside their permitted area (e.g., “You can only create events within 5 km of your current location.”).

5. Event Details Entry

Allow users to:
1.Enter the Event Name: Provide meaningful suggestions in the copy, such as:
“Include details like the occasion and location, e.g., ‘John & Jane’s Wedding, Lagos’.”
2.Select Event Type:
Offer a dropdown list of event types (e.g., Wedding, Funeral, Birthday, Corporate Event, etc.).
If a suitable type is not listed, allow the user to optionally type in a custom event type.
If no custom type is provided, default to “Other”.
3.Provide an Event Date:
Require the user to select a date for the event.
Constraints:
The event date cannot be in the past.
The event date cannot be set more than two weeks into the future.

6. Event Confirmation

Upon submission:
Confirm successful event creation with a message like, “Your event has been created successfully!”.
Display the Event ID prominently with a copy icon beside it for easy clipboard copying.
Add the copy icon functionality anywhere the Event ID is displayed throughout the app.
Visual indicator: Clearly show that the user has joined the event.

7. Post-Creation Redirection

Redirect options (same as for events found in discovery):
1.To Dashboard (if entered Event Creation directly).
2.To Image Upload (if entered from the upload pathway).

8. Developer Considerations

Geocoding and POI Services:
Use mapping APIs (e.g., Google Maps, OpenStreetMap, or Mapbox) to populate nearby POIs for step 3 and handle geocoding/address validation.
Explore configurable layers to prioritize landmarks like event centres, religious venues, and schools.
Location Restrictions:
Ensure configurable distance constraints for photographers (e.g., adjustable radius).
Event Types:
Maintain a dynamic list of event types in the backend to allow for updates.
Date Constraints:
Backend logic should enforce valid date constraints to ensure integrity, even if the frontend provides validation.

#EventFoto/MVP