Dive Buddy List Application

[enyaw]

From time to time I like most divers have run into the problem of finding a dive buddy. I'm thinking about developing a web based database application. It's time for a reality check before moving forward, does the following

1. Sound useful?
2. Accurately address the general issue?
3. Worth the time and effort to implement?

Problem Definition:
To develop an application that allows SCUBA divers to share contact information and find *Dive Buddies* base on specific criteria such as experience level, geographic location, and availability to dive. At the same time allowing an indiviedual diver to control how much personal information is shared.

Proposed Solution:
A web enabled data base application seems to be the most obvious solution to this problem. It allows divers that may not come into contact with each other through the normal course of events to find *compatable* dive partners, and provides a mechanisim to contact them. At the sametime combining the web with a databae engine will allow the individual diver to control how much contact information is released based on their individual comfort level.

 

[xSandman3]

PADI already has a version of this on their website. I haven't used it, but it looks like it would work fairly well.

 

[scubasean]

From time to time I like most divers have run into the problem of finding a dive buddy. I'm thinking about developing a web based database application. It's time for a reality check before moving forward, does the following

1. Sound useful?
2. Accurately address the general issue?
3. Worth the time and effort to implement?

Problem Definition:
To develop an application that allows SCUBA divers to share contact information and find *Dive Buddies* base on specific criteria such as experience level, geographic location, and availability to dive. At the same time allowing an indiviedual diver to control how much personal information is shared.

Proposed Solution:
A web enabled data base application seems to be the most obvious solution to this problem. It allows divers that may not come into contact with each other through the normal course of events to find *compatable* dive partners, and provides a mechanisim to contact them. At the sametime combining the web with a databae engine will allow the individual diver to control how much contact information is released based on their individual comfort level.

It may be of some use. But I've found that it is often easiest to find dive buddies by scoping out the local clubs, talking to local divers, going on scubaboard, etc.

Geographic location would have to be fairly narrow to work. Divers 100 miles apart aren't very likely to dive together, unless they generally dive the same locations.

Also, such a database is only as good as the data inside. You'd have to have lots of people go there often. Or, you'd want to possibly somehow make it a link off of SB....

 

[H2Andy]

i've seen a few online. the problem is you have to get a ton of divers to register
and so on...

but it's a good idea. good luck.

 

[ScubaTexan]

PADI already has a version of this on their website. I haven't used it, but it looks like it would work fairly well.

I've had divers contact me from my PADI profile, but when I contact them back about diving with them, I never hear from them again.

 

[enyaw]

What I've Picked-up so far:

Good Idea (may not be practical)
Location information critical
At least some have experienced less than stellar results from nationally based list.

Question: Would developing something that was regionally or club based have a greater chance at success?

Listed below are proposed fields (if I decide to move forward), Is anything missing?

Data Elements:

1) Last Name (required)
2) First Name (required)
3) Address (Street, City, State, Zip, Country) (required)
4) Phone (required)
5) Email (required)
6) Web Address
7) Picture
8) Certification Level (required)
9) Certification Organization
10) Certification ID
11) Total Bottom Time
12) Number of Dives (required)
13) Interests
14) Availibility to Dive
15) Diver control of which elements are shared

a) Address & Zip Code
b) City
c) State
d) Phone Number
e) Web Address
f) Email Address
g) Record Active/Inactive​

16) Administrative Active Record Flag​

 

[scubasean]

Let me ask *you* a question...

Are you trying to solve a problem (people finding a buddy)?

Or are you trying to find a problem you can solve with a database application?

Sounds like the latter. If so, I wouldn't recommend your approach.

But, go for it!

What I've Picked-up so far:

Good Idea (may not be practical)
Location information critical
At least some have experienced less than stellar results from nationally based list.

Question: Would developing something that was regionally or club based have a greater chance at success?

Listed below are proposed fields (if I decide to move forward), Is anything missing?

Data Elements:

1) Last Name (required)
2) First Name (required)
3) Address (Street, City, State, Zip, Country) (required)
4) Phone (required)
5) Email (required)
6) Web Address
7) Picture
8) Certification Level (required)
9) Certification Organization
10) Certification ID
11) Total Bottom Time
12) Number of Dives (required)
13) Interests
14) Availibility to Dive
15) Diver control of which elements are shared

a) Address & Zip Code
b) City
c) State
d) Phone Number
e) Web Address
f) Email Address
g) Record Active/Inactive​

16) Administrative Active Record Flag​

 

[JimC]

3) Address (Street, City, State, Zip, Country) (required)
4) Phone (required)
5) Email (required)

A few thoughts on these items.
- Street is definatly not required, and should be optional.
- Dito on phone and email
- Use some sort of public/private toggle on the more sensitive data items
- Use the application to send the e-mail, so that the sender can't directly access the information without consent.


Do your bit for internet privacy.