Make a chat app (broadcasting) using inertia (api resources) which sends an email (mail) when you miss a message. Have events to clean up notifications etc when you interact with a chat
Project idea for improvement Laravel skills
Hi,
I will develop a project to improve my Laravel skills and I want to use all the goodies that Laravel offers us (Events, Mail, Broadcast, API Resource, Helpers, Providers, Requests... etc.).
What do you think should be the structure and idea of such a project?
hello @Sinnbeck i use crisp . but isnot good tutorial that i understand how use environment chat it in my site. i just use chatbox in my site
@LoverToHelp I wrote my own using those tools :)
@iforeman Pick something you’re interested in and build something with it.
Part of growing as a developer is not having to be spoon-fed everything. This includes project ideas. Employers want to see people who can think for themselves.
Have a look here
You will find two projects with the code provided, you build them yourself and compare your code
- Beginner Demo-Project: Personal Blog
- Advanced Beginner Demo-Project: Simple CRM
These two projects cover most of the things you will encounter in each project like Routing (caching, rate limiting, route model binding...), Eloquents (one to one, one to many, many to many, polymorphic relationships...), Form Validation (using the normal validator and form requests...), File Upload, Authorization (gates, policies, using packages...), Custom Middlewares, APIs, Debugging tools, Sending emails and notifications and much more..
Here are a few of my pet projects, again interests as mentioned before... and things I THOUGHT would be fun...
- wedding website... has a frontend to show the normal stuff, also a guest management to send invites, track table arrangements, etc.
- shopping lists app. [our household uses this everyday]
- stock (option) trading app
- emulation of Basecamp
- sms notification channel for ClickSend. This is a package. Its a recent interest, the idea of developing packages, I actually think this is an interesting way to understand how laravel works. What I am liking is there are plenty of things I realized id like to share across projects and then I end up copying and pasting those chucks of code. Having a package where I can manage that code and share it once is cool.
Next, I am working on a personal finance app that uses the Plaid api
In the past, I wrote a lot of code that was project specific. Like a wedding website. Once the wedding is over its kinda of useless to me. For work, I've writing apps that source off-market real estate, and more recently an aggregator of businesses for sale. But I've moved to wanting to build things that are more agnostic and interchangeable.
Still exploring this. But its why I decided to write an emulation of Basecamp, more of a general project manager. Then if I want to write one off things for projects I have my own code base that allows that. My view of programing used to be that that was the WHOLE point, write custom stuff.
I guess what im saying is I have sooo much time and code in projects that are gone and done. I want to write more things that I can reuse.
Please or to participate in this conversation.