Quote (oOn @ Sep 30 2013 12:56pm)
Although those are some good points, I still disagree. in my data structures class I made a jav program that uses a gui to input files and then uses a huffman algorithm to compress and/or decompress files, and i think it looks good on a resume. The point isnt to make money, but to make a nice program that can do what the objectives aim to do. I would be willing to work longer if I can find a dedicated partner
I would like to also eventually make an app, although I think that requires more creativity and work
honestly it doesn't. if you apply to a normal app-development company, showing that you can implement fancy algorithms someone else designed really doesn't hold any value. i've seen people put school projects based on algorithms on their resume, which is fine if you have zero work experience. but if they have work experience, i usually laugh that they included it. much more valuable would be classroom experience with sql (jdbc/jpa), frameworks (j2ee, jsf, threads, REST/SOAP, etc), and libraries (gson, log4j, xstream, etc) since that's closer to what most companies will use. on the other hand, if you didn't something really interesting with it (eg: not your basic huffman encoding), then it can be included.
if you apply to a company where algorithms are more important, than they expect you to already be familiar with algorithms and be able to use them; in fact their entire interview process will be algorithms. putting it on your resume won't win any brownie points.
with that said, it's good that you're trying to do something outside of school. the one you picked shouldnt take very long though, so i dont see the value in collaboration. i would agree with eyewuvd2 that making a phone app would be more useful, if you're up to it.