Celer Sight AI is a platform that tremendously speeds up image analysis for life sciences. It uses AI models that adapt to the user's data for perfect ROI's and is designed with a simple and intuitive user interface.

My goal in developing the landing page for Celer Sight AI was to establish its online presence and clearly highlight its benefits over other image analysis platforms.

In addition to the landing page, the project required an authentication system, role based authorization and comprehensive dashboards for both users and administrators. The user dashboard needed to facilitate management of personal accounts, teams, and lab activities. The admin dashboard, on the other hand, was designed to oversee user accounts and provide support, assisting them in their projects. These functionalities were essential for ensuring an efficient and user-friendly experience for every interested party.

To ensure my ideas aligned with the client's vision, prototyping and wireframing were essential steps before initiating the design process.

These tasks were carried out in Figma, and following a few iterations, I proceeded to the development and testing stages.

The application leverages Next.js on the front-end, integrating the App Router to manage the rendering of various application segments as server or client components. This approach allows for enhanced control that can boost SEO and performance. The Next.js application is supported by a separate Express.js back-end with MongoDB.

TailwindCSS and Radix UI style the app, simplifying and speeding up component customization. Additionally, Shadcn UI provided a selection of premade components that proved to be quite useful.

Jest with Supertest/Cypress were used for API unit/end-to-end testing respectively.

Additionally, external services and APIs were integrated, such as SendGrid for email, Sentry for issue tracking and Azure blob storage for media storage.

While Vercel's seamless deployment experience made it the ideal platform for hosting the Next.js front-end, the anticipated cold starts and expected limited traffic early on, led me to opt for a separate Express.js back-end. Additionally, in startups where the product is still evolving, the flexibility of a separate back-end allows for easier changes and iterations.

After exploring various component libraries, I lean towards Tailwind UI combined with an unstyled primitive library such as Radix UI for the flexibility and productivity boost they offer.

Since the project is constantly evolving, future features may include the integration of a subscription system, a blog, and a mobile app.