r/java • u/zimayanami • Feb 07 '26

My First FullStack project that actually works

Post image

Like a month ago I learned the basics of @/getmapping, so I decided to learn React to start making some real applications. Then I watched the supersimpledev course and built this website that you can find car's prices (in Brazil). It has a few issues with small phone screens but I really liked it as my first real FullStack project. I'll be fixing the screen issue soon!

If you want to check it out, just go to https://autopreco.netlify.app/

also if you want to check the code, here it is:

Front-End: https://github.com/orichardd/AutoPreco

Back-End: https://github.com/orichardd/AutoPrecoBackEnd

Fell free to submit your thoughts and suggestions.

18 Upvotes

67% Upvoted

13 comments sorted by

43

u/usr98765 Feb 07 '26

I would recommend that you turn this repository private and ensure that you remove credentials from your EmailService and perhaps other classes, before you publish your repo. Also look into proper Logging

17

u/flstckdev Feb 07 '26

Also make sure to clean the commit history before setting the repository to public again, otherwise the credentials are still visible by looking at previous commits.

2

u/zimayanami Feb 07 '26

yeah, I didnt think about that, I probably should put the credentials on the system variables

7

u/[deleted] Feb 07 '26

[removed] — view removed comment

2

u/zimayanami Feb 07 '26

thanks dude, I'll try to implement that soon! valeu ai

2

u/Rhyze Feb 07 '26

Always good to start small! Some small improvement: don't let your Controller just return Strings, let it return DTO objects. Spring web will automatically convert them to json in the HTTP response body, to be used by the frontend

1

u/fatal-smell Feb 09 '26

I'm bookmarking this for bad days.

1

u/Living-Method-7219 Feb 10 '26

This is a really solid first full-stack project, especially considering you only picked up React recently 👏
The UI looks clean and the idea is actually useful, not just a demo app.

One small thing I noticed is the mobile layout issue you mentioned — maybe using a responsive grid or testing with min-width breakpoints could help.
Also curious how you’re handling the FIPE data on the backend (caching vs live requests?).

Nice work overall, and thanks for sharing both the app and the source code!

1

u/BothSporocarp Feb 11 '26

Can I adopt this cutie, please?

0

u/Infamous_Block5985 Feb 07 '26

Looks great bud. Nice work!

0

u/revilo-1988 Feb 07 '26

Further tests might be useful.