Next JS AAC

[Karimm]

Hi everyone, I lost my old account here so I had to create a new one.

I decided to start a new AAC project for fun/learning since I've been working with React for the last 3 years, it will use the latest technology with no compromises,
my end goal is to open source it for the community since I learned a lot here.

Current tech stack:
Next JS 14
Prisma
Tailwind
Shadcn (headless UI)
Zod
React-hook-form
Typescript
Auth JS using JWT for authentication

I have a repo but there's not much to show yet.

Few screenshots from what I got done in a week

​

Currently trying to keep the components split as much as possible to leverage server side rendering, forms are done using server actions, created modules for every route so code is much more readable and maintainable.

Layout will be responsive for different screen sizes

I would love to hear your opinions and concerns.

 

[Fjorda]

Cool, great job!

Unfortunately just like the other newer AAC's, any form of React/Node/Next JS framework will take a long time to gain any real traction.

The main reason being not many are familiar with such a tech stack, which will limit any productive use for the average OT owner. PHP AAC's will always be the go-to.

However, as a full stack dev myself, it's nice to see and I hope you finish this fully just for personal experience

 

[Karimm]

Cool, great job!

Unfortunately just like the other newer AAC's, any form of React/Node/Next JS framework will take a long time to gain any real traction.

The main reason being not many are familiar with such a tech stack, which will limit any productive use for the average OT owner. PHP AAC's will always be the go-to.

However, as a full stack dev myself, it's nice to see and I hope you finish this fully just for personal experience

I agree, people are comfortable with the current AAC projects because they've been around for so long.

My goal is not to have OT owners using it, but to introduce a new option for people who actually know what these technologies offer.

 

[Niebieski]

I agree, people are comfortable with the current AAC projects because they've been around for so long.

My goal is not to have OT owners using it, but to introduce a new option for people who actually know what these technologies offer.

If not OT owners are being targeted to use this, then who? OT players?

 

[Karimm]

If not OT owners are being targeted to use this, then who? OT players?

Sorry if my point wasn't clear enough, of course it will be an option for OT owners but I don't think they would want to replace the current PHP AAC it's stable and it gets the job done.

new AAC will introduce a learning curve, so I think this will not be the best option for owners who don't want to bother with a new AAC regardless of the technologies.

 

[Marceklos]

I'd love to see it.
Will you push it to repository?

 

[Karimm]

I'd love to see it.
Will you push it to repository?

GitHub - karimadnan/KarimAAC

Contribute to karimadnan/KarimAAC development by creating an account on GitHub.

github.com

Pushed all the changes

 

[Karimm]

Creating account & Character is working

It redirects & login on success

Going to implement email verification and 2FA next

https://imgur.com/iyYaGFL

Normal login

https://imgur.com/tniwCsK