Market for SSL for BREW 1.x?

[Murray Bonner]

Hi:
[I post this here since "application ideas" are listed as acceptable content for this thread..]

I'm currently working on an app. that needs SSL. I know it's avail. in BREW 2.x+. It would be a shame to ignore all those 1.1 handsets that will be out there for at least another year.

I've found a tiny SSL implementation for embedded devices and, in partnership with the original developer, I'm considering porting it to BREW and selling it as an extension.

The big question is, will anyone be interested?

Please let me know your thoughts.

Thanks!

Murray

[accolade]

For us, I guess it all depends on the price point.


Hi:
[I post this here since "application ideas" are listed as acceptable content for this thread..]

I'm currently working on an app. that needs SSL. I know it's avail. in BREW 2.x+. It would be a shame to ignore all those 1.1 handsets that will be out there for at least another year.

I've found a tiny SSL implementation for embedded devices and, in partnership with the original developer, I'm considering porting it to BREW and selling it as an extension.

The big question is, will anyone be interested?

Please let me know your thoughts.

Thanks!

Murray

[Murray Bonner]

Thanks for the response.

Could you please give me some feedback w/r/t price?

(I know I sound like a used-car salesman here :o ) What price point would make it viable for you? Would 10% with a $0.20 floor work? (I throw this out there for discussion purposes only. This should not be construed as a pricing commitment as I've yet to discuss pricing with my prospective partner)

Thanks,
MB

[accolade]

For full source code access, a good API, we could be willing to shell out a few hundred USD. I would not be interested in a revenue-sharing scheme, even if the numbers are fair -- just too much "hassle".

Btw, had you plan to make the SSL into a public BREW extension?

Also, if you got a really good SSL implementation, you may want to consider hitting the OEMs or Qualcomm directly with your implementation.


Thanks for the response.

Could you please give me some feedback w/r/t price?

(I know I sound like a used-car salesman here :o ) What price point would make it viable for you? Would 10% with a $0.20 floor work? (I throw this out there for discussion purposes only. This should not be construed as a pricing commitment as I've yet to discuss pricing with my prospective partner)

Thanks,
MB

[Murray Bonner]

For full source code access, a good API, we could be willing to shell out a few hundred USD.
Are you sure your parents would let you spend your WHOLE allowance? PM me your contact info and I'll pass it on to the company that owns the source, along with your offer. I think it would be a good idea for you to stay close to the phone Monday morning cuz I've NO doubt their CEO is gonna want to talk to you! :rolleyes:

I would not be interested in a revenue-sharing scheme, even if the numbers are fair -- just too much "hassle".
Apparently you're not quite clear on the BREW Extensions concept.

[accolade]

That's funny. Well, I do know a little bit about BREW public extensions, but it does not mean I would want to share my revenue with an extension developer ;)

The thing is, SSL is not rocket science, and unless you are providing compelling values, why would I pay much for it? Is your implementation really going to make *THAT* much of a difference?

And like you said, SSL is available in later BREW versions...

You were looking for market feedback, well, you got one data point... :D


Are you sure your parents would let you spend your WHOLE allowance? PM me your contact info and I'll pass it on to the company that owns the source, along with your offer. I think it would be a good idea for you to stay close to the phone Monday morning cuz I've NO doubt their CEO is gonna want to talk to you! :rolleyes:

Apparently you're not quite clear on the BREW Extensions concept.

[Murray Bonner]

Well, I do know a little bit about BREW public extensions, but it does not mean I would want to share my revenue with an extension developer ;)

Then you simply won't get the use of *ANY* extension developer's product, because the revenue sharing model is the whole idea. I don't get where the "hassle" comes in -- the BREW distribution system handles payments to the extension developer, just like it handles payment to the extension user. The two partys' bean counters never need to interact.

That said, there's certainly nothing wrong with building your own wheel, provided that the economics make sense or the wheel you need just doesn't exist.

The thing is, SSL is not rocket science, and unless you are providing compelling values, why would I pay much for it? Is your implementation really going to make *THAT* much of a difference?

Sorry, I had no idea I was dealing with a crypto expert. You must eat number theory for breakfast. If you can get a 35K SSL implementation, complete with a 5 algorithm cipher suite that includes AES, banged out for a few hundred bucks, without violating copyright, more power to ya! Let me guess, you'd get it done offshore?

As for the implementation making a difference, I suppose you're right, if you don't mind foregoing the few million BREW 1.1 handsets that are out there. Further, several handsets don't implement the ICipher interface, so the fact that this implementation exposes all its crypto algo's (that go way beyond ARC4) might make it attractive to some.

As for the data point you've provided, thank you. I think I'll consider it an outlier.

[ruben]

The thing is, SSL is not rocket science, and unless you are providing compelling values, why would I pay much for it? Is your implementation really going to make *THAT* much of a difference?

It takes quite a bit of effort and expertise to build SSL implementation for mobile device and keeping in mind about copyright issue.

You want source code with good extension API, and don't want to do revenue sharing(Brew distribution system takes care of it) for COUPLE OF HUNDRED DOLLARS, kind of interesting proposal :confused:
Do you work as offshore contracting company for big content company or third party developer?

[accolade]

Nothing exists as an island and for every problem, there are often a multitude of solutions.

For us, an SSL implementation on BREW 1.x is not worth much.

Good luck with your SSL quest though. :)

It takes quite a bit of effort and expertise to build SSL implementation for mobile device and keeping in mind about copyright issue.

You want source code with good extension API, and don't want to do revenue sharing(Brew distribution system takes care of it) for COUPLE OF HUNDRED DOLLARS, kind of interesting proposal :confused:
Do you work as offshore contracting company for big content company or third party developer?

[accolade]

Btw, with a couple of hundred dollars, I meant a couple of hundreds dollar per seat/app, like the $1500 for the ARM compiler per seat.
:D

Nothing exists as an island and for every problem, there are often a multitude of solutions.

For us, an SSL implementation on BREW 1.x is not worth much.

Good luck with your SSL quest though. :)