I have often been asked for project ideas for summer / final year projects. Here’s my take based on my academics & interviews that I have been through.
But I want my project to be hatke
#1, be observant.
Most of the project ideas you’ll get, is by observing. Observe the community, people, college NGOS’s around you.
Talk with people, college faculty and get to know any real life problem they are facing. Any project that you would build would be rendered excellent, if it solves any real life problem.
#2 How to? thoughts.
We live in the era of constant information flow. Be it mobile, desktop or web based application. Analyse them. If you find any information flow gap, your next project could be the solution to it.
#3 Why not this? thoughts.
Mentally challenge the way current information is processed and try to figure out alternative solutions.
I don’t want any management system app man, my guide would straightaway reject it!
It’s not necessary that you need to develop a project which has unique idea. Any idea which exists, but you have a better methodology or technology stack in mind that you think could make it more better in terms of expense, resource utilization or human intervention, go for it!
Making the existing applications mobile
If you have a old project, or have access to old project that was developed years ago, but was useful only as a desktop application or a web application, mould it to become API driven make it work with mobile devices!
Make existing applications intelligent
If you wish to make data science driven projects then its best to work on old applications that have been developed long ago, with loads of data. Use tools, open source data and techniques.
Make / create existing applications IoT driven
With maturity in IoT based devices, platforms (servers / machine Learning based APIS) and the related kits available, its not really difficult to develope IoT based applications.
Make existing applications distributed
If you make your projects capable to handle the performance in distributed way, doesn’t that sound great?
I want to build a project on xyz tech stack because it sounds cool ( also I don’t know where to start :( )
Learning a new technology is definitely not wrong, but only because it sounds cool and not its relevance with the project needs, like if you plan to use NoSQL datastores in a project where you need transaction based records, you should think again.
Don’t just write code that makes your application work, learn
-> core/theory/internals of the technology and not just the syntax/structure of it.
-> widely used coding conventions in the language you are writing the code for
-> and apply design patterns
-> code collaboaration
-> to question why?
This is just a glimpse of bare minimal options for technology stack you can use.