DEV Community

Salisu Adeboye
Salisu Adeboye

Posted on

I Built Taskora with .NET and React — I’d Like Developers to Try It

I’ve been building Taskora, a full-stack project and task delivery platform using .NET, C#, React, TypeScript and PostgreSQL.

It started as a simple todo application, but I kept extending it around a question:

What would it take to turn a basic task application into something closer to a real project delivery system?

Taskora now supports:

  • Workspaces with Owner, Manager and Member roles
  • Project and task management
  • Sprint planning
  • Drag-and-drop delivery board
  • Task assignment and workflow rules
  • Personal My Day todos
  • Daily routines
  • Project health and risk tracking
  • Reports and delivery calendar
  • Due-date reminders
  • In-app and email notifications
  • Background jobs
  • Operational monitoring and health checks
  • Role-based access control

The Stack

The application is built with:

Backend

  • .NET / C#
  • ASP.NET Core
  • Entity Framework Core
  • PostgreSQL

Frontend

  • React
  • TypeScript

Production

  • Vercel — frontend
  • Render — .NET API
  • Neon — PostgreSQL

The backend follows a modular monolith architecture with separate Domain, Application, Infrastructure and API layers.

I deliberately kept it as a modular monolith rather than splitting it into microservices before there was a genuine reason to do so.

But I'd Rather You Try It

Instead of only writing about what I built, I’d like developers to actually use it and tell me what they think.

🌐 Live demo

https://taskoraz.vercel.app

Click View demo on the landing page and choose a role.

You can explore Taskora as:

  • Super Admin
  • Workspace Owner
  • Manager
  • Member

The demo workspace uses fabricated data and is isolated from real user accounts.

Note: The .NET API currently runs on Render's free tier, so the first request after a period of inactivity may take a short moment while the service wakes up.

Source Code

The entire project is available on GitHub:

https://github.com/bhoyee/Taskora

If you're a .NET, React or software engineer, I'd especially appreciate feedback on:

  • Architecture
  • User experience
  • API design
  • Project structure
  • Security
  • Testing approach
  • Features that feel unnecessary
  • Features you think are missing
  • Anything you would redesign differently

Don't worry about being polite about the technical decisions. 😄

I'm more interested in finding weaknesses and improving the system than hearing that everything looks good.

If you had to change one thing about Taskora before considering it production-ready, what would you change?

Top comments (0)