Java Project Partner

S

Supremacy

Active Member
Joined
Jun 17, 2006
Messages
32
Reaction score
0
Hey,

I've been working on a mobile chat client (called Banana) and server the past few months, and have got a decent version working (including contact lists, invites, blocking contacts, moods, online status and new: Facebook-life statuses). However, if any of you have worked on a large-ish project before, you would know the feeling of "what do I do here" or "whats the best way to do this...". I've been getting these feelings quite a lot lately, and a second opinion / advice is ALWAYS welcome, so I have decided to put out a search to find another decent Java or more preferably J2ME programmer to help with the project development.

If you fit this criteria and are interested in helping out in such a project, please do let me know, as I would welcome a partner. Of course, if this program does make it big, a deal can be worked out as to how things are shared! :)

You can see some images of development at http://www.facebook.com/group.php?gid=93151523893 . Feel free PM me here or message the group creator on Facebook.

Thanks!

PS: I am also looking for a few beta testers, as I need to know which phones are compatible, and any bugs you may find.
 
Best of luck mate before some nutter try a flame you. Don't give up and don't be put off on how competitive the market is. Also your building yourself up a wonderful CV if you ever need to find a job. J2ME skills are always in demand.

Suggestion, also play around with bluetooth to ad some extra functionality to your app, say perhaps a piconet only chat session - don't think anybody does that yet.

Keep well
Christopher
 
lol what a name, classic... Banana - Open a new Peal Into the next generation of mobile instant messaging..;)
 
My first thought with this is stress test your software and server a lot before release.

You don't want to release it then go viral and find you can't cope with the demand.
 
AcidRaZor said:
My first thought with this is stress test your software and server a lot before release.

You don't want to release it then go viral and find you can't cope with the demand.
Click to expand...

Yes, of course. This is still very much in development. Stress testing will start when I am happy with the client for a release, then tests will commence, which is why I need beta testers :)
 
It looks nice, are you using a custom protocol or implementing something like jabber?

I would like to help as I do have j2me experiance (though old) but I do not have time at the moment unfortunatley
 
Veroland said:
It looks nice, are you using a custom protocol or implementing something like jabber?

I would like to help as I do have j2me experiance (though old) but I do not have time at the moment unfortunatley
Click to expand...

No, its all custom protocol. The jabber message protocol has rather large message sizes, which leads to more airtime use per message. MXiT found this out the hard way after a few years.
 
Supremacy said:
No, its all custom protocol. The jabber message protocol has rather large message sizes, which leads to more airtime use per message. MXiT found this out the hard way after a few years.
Click to expand...

yep, but it does allow for many other apps to use the same netswork. GTalk for example also uses jabber protocol
 
Veroland said:
yep, but it does allow for many other apps to use the same netswork. GTalk for example also uses jabber protocol
Click to expand...

Originally I was going to use the jabber protocol, along with an already made server such as Openfire, but this was supposed to be a personal project of mine to learn Java, which I did :P I thought I would learn more by doing it my way instead of just copying another code.
 
Supremacy said:
Originally I was going to use the jabber protocol, along with an already made server such as Openfire, but this was supposed to be a personal project of mine to learn Java, which I did :P I thought I would learn more by doing it my way instead of just copying another code.
Click to expand...

I've used Openfire before, it's fairly nice
 
I found Netbeans to be the best for me, and it got even better when I found the mobility plugin. As for emulators, I use JME SDK 3.0 and J2ME Wireless Toolkit. JME being better as you can emulate it for various phones and their Java versions.
 
Nice, I have never found a liking in Netbeans and prefer eclipse. Also used the J2ME wireless toolkit last time I was playing with it. Wrote a app thats connects using HTTP to a J2EE app running on a Websphere server st my office which downloaded my mail for me. Not very useful but I did it to learn. Did some more J2ME apps after that for work purposes but it was a few years ago.
 
Supremacy said:
Yes, of course. This is still very much in development. Stress testing will start when I am happy with the client for a release, then tests will commence, which is why I need beta testers :)
Click to expand...

I definitely wouldn't leave stress testing until beta. You'll be surprised how inefficient frameworks & runtime environments (esp Java & i'ts VM) can be.

You could end up doing a LOT of rework.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X