Do we have mobile infrastructure for iOS and Android?

Started by clayop, February 27, 2016, 10:37:28 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Chris4210

Yes, we developed a couple of wallets which can be used already today. Currently, they are all Android since the Apple App store is so restrictive and does not let our wallet in. We are working on that issue too.
Vote Chris4210 for Committee Member [url="http://bit.ly/1WKC03B"]http://bit.ly/1WKC03B[/url]! | [url="//www.payger.com"]www.Payger.com[/url] - Payments + Messenger | [url="//www.bitshareshub.io"]www.BitShareshub.io[/url] - Community based fanpage for the BitShares Blockchain

jakub

Quote from: clayop on March 01, 2016, 09:44:23 PM
Quote from: xeroc on March 01, 2016, 08:53:55 PM
The answer to your question is: Yes.

The current web wallet does it the same way. The private key never leaves the browser on the clientside

I think we'd better have native library for Android and iOS. If we restrict ourselves in "wallet", current state is okay IMO. But if we want to expand our services to the blue ocean, we need native libraries.

@clayop
It looks like @kenCode has recently done the heavy lifting with native Android:

Quote from: kenCode on May 31, 2016, 08:17:10 PM
Quote from: jakub on May 31, 2016, 07:40:45 PM
Quote from: kenCode on May 31, 2016, 07:04:27 PM
It is native android so it runs extremely fast.
Is it native Android connected to the hosted wallet infrastructure of the OpenLedger server?
If so, does it mean you've ported the whole client-side JavaScript code-base to native Android?
Ported, no. This has been written from scratch. You guys can see the code in a few weeks when I upload everything to github for forking etc :)


clayop

Bitshares Korea - [url="http://www.bitshares.kr"]http://www.bitshares.kr[/url]
Vote for me and see Korean Bitshares community grows
delegate-clayop

clayop

Quote from: xeroc on March 01, 2016, 08:53:55 PM
The answer to your question is: Yes.

The current web wallet does it the same way. The private key never leaves the browser on the clientside

I think we'd better have native library for Android and iOS. If we restrict ourselves in "wallet", current state is okay IMO. But if we want to expand our services to the blue ocean, we need native libraries.
Bitshares Korea - [url="http://www.bitshares.kr"]http://www.bitshares.kr[/url]
Vote for me and see Korean Bitshares community grows
delegate-clayop

xeroc

The answer to your question is: Yes.

The current web wallet does it the same way. The private key never leaves the browser on the clientside

testz

Quote from: clayop on February 27, 2016, 10:37:28 PM
Can mobile users connect any graphene websocket server, and send transactions with having their private keys only in their devices?
Do we have such APIs? (or kind of develop infrastructures)

This is what OPENPOS do https://bitsharestalk.org/index.php/topic,20762.0.html
Sources you can find here: https://github.com/kenCode-de/bitshares-wallet

clayop

Can mobile users connect any graphene websocket server, and send transactions with having their private keys only in their devices?
Do we have such APIs? (or kind of develop infrastructures)
Bitshares Korea - [url="http://www.bitshares.kr"]http://www.bitshares.kr[/url]
Vote for me and see Korean Bitshares community grows
delegate-clayop