Contact Management Web App Development

AccuLine Contact Management App Requirements:

1. App Overview
This web-based app is designed for tracking interactions with key contacts. The app will allow the user (sinfge user) to add, manage, and track interactions with various contacts. It is crucial that only I, as the user, can access this app, and that no public access is permitted.

2. App Structure
The app consists of the following core components:
- Home Screen: Displays the main options like adding contacts, viewing a contact list, managing fields, and interaction history.
- Add Contact Screen: Input fields for contact details (name, email, phone, company, etc.).
- Contact List Screen: A sortable, filterable list of all added contacts, which links to individual contact cards.
- Interaction List Screen: Displays all recorded interactions, including the ability to sort/filter by date, contact, and status.
- Contact Card Screen: Displays all details of a specific contact, including past interactions.
- Manage Fields Screen: Allows customization of dropdowns (vendor type, interaction type, etc.).

3. User Access and Security
Since this app will only be accessed by a single user, we want to avoid setting up a full user management system. Instead, the app should be secured using HTTP Basic Authentication to prevent unauthorized access.

Steps for Developer:
- Implement HTTP Basic Authentication on the server where the app is hosted.
- Use a simple username and password mechanism to restrict access.
- Ensure the app is served over HTTPS to encrypt the authentication process and data transmission.


4. Email Notifications
The app will send an email reminder when a future interaction date is set.
- Email should be sent at 9 AM Israel time on the day of the event.
- Use the default email application configured on the device to trigger these notifications.


5. User Interface
- The UI should be clean and simple, allowing for easy navigation and use. No advanced design or aesthetics are required.
- Focus on usability and quick access to information (contacts, interactions).


6. Additional Notes
6.1. Security Measures: In addition to HTTP Basic Authentication, ensure that the app is served via HTTPS for secure data transmission.
6.2. Mobile Compatibility: While the app will primarily be accessed via Safari on iMac, it would be ideal if the interface adjusts for use on iPad or iPhone as well. This is not must if additional costs are required.
6.3. Scalability: The app is designed for single-user access but consider future scalability in case additional features or users need to be added.

Attached is a description of the app's screens. This is just a general concept. We're looking for someone to turn this into a solid, user-friendly product that will help us achieve a smooth and efficient user experience.