Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate Entire App to Remix for Simpler and Faster Development #233

Open
naimulcsx opened this issue Nov 17, 2024 · 0 comments
Open

Migrate Entire App to Remix for Simpler and Faster Development #233

naimulcsx opened this issue Nov 17, 2024 · 0 comments

Comments

@naimulcsx
Copy link
Owner

Migrate Entire App to Remix for Simpler and Faster Development

Background

This project was initially conceived during my university days, a time when I was deeply focused on building technically impressive systems. While that approach was valuable for learning and exploration, I’ve grown and matured as a developer since then. I've come to realize that a simpler, more pragmatic approach is often more effective in driving progress and delivering results.

The previous app setup, while architecturally sound and robust from an engineering standpoint, has proven to be overkill for our current needs. It has resulted in slower progress and a lack of momentum in pushing features aligned with the roadmap. Given our current stage, simplicity and speed must take priority over maintaining a complex and highly engineered setup.

Objective

We are migrating the entire application to Remix with the primary goal of simplifying the development workflow and accelerating feature development. This migration will eliminate the need for a separate API server and allow us to handle backend operations directly in Remix loaders and actions.

Plan

  1. Migrate Frontend: Transition the frontend codebase to Remix, leveraging its capabilities to manage routing, data fetching, and rendering.
  2. Consolidate Backend Operations:
    • Remove the separate API server.
    • Handle all backend operations (data fetching, mutations, etc.) within Remix loaders and actions.
    • Integrate database calls directly within these functions, where appropriate.
  3. Streamline Setup:
    • Reduce setup complexity and dependencies.
    • Ensure the new stack is easier to onboard for new contributors and maintainers.
  4. Maintain Functionality: Retain all core features and functionality during the migration, ensuring no regressions.
@naimulcsx naimulcsx pinned this issue Nov 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant