Author Topic: Do we have mobile infrastructure for iOS and Android?  (Read 2431 times)

0 Members and 1 Guest are viewing this topic.

Offline Chris4210

  • Sr. Member
  • ****
  • Posts: 431
  • Keep Building!
    • View Profile
    • www.payger.com
  • BitShares: 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 http://bit.ly/1WKC03B! | www.Payger.com - Payments + Messenger | www.BitShareshub.io - Community based fanpage for the BitShares Blockchain

jakub

  • Guest
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:

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 :)

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
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 - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: 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

Offline testz

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

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: 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 - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop