Hi everyone,
I’m working on a museum membership card software project and would appreciate some feedback from developers who have built similar visitor management or membership systems.
The front end is built with HTML, CSS, and JavaScript, while the backend uses ASP.NET Core (.NET) with a relational visitor database. The platform manages digital membership cards, member profiles, renewals, QR code validation, and visitor records.
One challenge we’re focusing on is keeping the system responsive as the number of members grows. We’re optimizing database queries, API performance, and the UI so staff can quickly search members, verify memberships, and process renewals during busy visitor hours.
For those with experience building CRM or membership applications:
- How would you structure the visitor database for long-term scalability?
- Which .NET practices have made the biggest difference in performance?
- Have you implemented caching or background jobs for renewals and notifications?
- What HTML/CSS techniques have improved usability for staff working at admission desks on different screen sizes?
We’ve been testing these ideas while building https://membershipanywhere.com/digital-membership/, and it’s been interesting to see how much database design affects the overall user experience.
I’d love to hear what architecture, tools, or best practices have worked well for your projects.