search

cabal-club / commons

high level thoughts and issues for the future of cabal
14 stars 2 forks source link

mobile client? #17

Open ghost opened 3 years ago

ghost commented 3 years ago

any plans for an android/ios client? I can't really convince my friends to switch from telegram to cabal if we can't use it while we're outside

cblgh commented 3 years ago

@horusra yes there are plans :)

we currently have a slow-moving wip on a web-based client. once that is working, a few of us wanna take the base of that work and shove it into react-native land :)

dpriskorn commented 3 years ago

I have yet to find a snappy, well working react-native app. I suggest creating a fast cabal core implementation in Rust and create an UI in kotlin like Sunrise Choir did with ssb.

okdistribute commented 3 years ago

@egils-consulting that's a great idea and will also take a quite bit more time to complete. Mapeo is react-native and it is pretty snappy; but react-native does require paying attention to not bloat it down.

dpriskorn commented 3 years ago

Yeah. How hard would it be to write a rust implementation? Is the cabal protocol well documented somewhere?

hackergrrl commented 3 years ago

On 08/22 00:02, Egil Priskorn wrote:

Yeah. How hard would it be to write a rust implementation? Is the cabal protocol well documented somewhere?

The cabal parts wouldn't too hard to port I bet, but the underlying stack (hypercore, multifeed) are BIG and complex. There's some work being done on a hypercore rust implementation (I think by @Frando!), so once that's finished I think a cabal port might be feasible.

dpriskorn commented 3 years ago

I will see if I can help out and learn some more rust :)

ghost commented 3 years ago

Yeah I would also like to suggest not going the react-way as it's better to go with rust for long term and performance benefits. I also want to add you guys are doing great work!