The current mobile UX is very bad. The way to approve it is to implement a light client and wallet at the OS level.
Scope:
options for development:
options may not be all that different, since the implementation is done with apps, rather than integrated directly in the OS. So we can potentially create light client app and integrate into either OS.
Fork grapheneOS, using ethOS implementation as a reference.
Important question: is the priority UX or security?
android will sacrifice security (slightly) for better UX
grapheneOS will sacrifice UX slightly for better security
Chosen solution: Fork grapheneOS and add in starknetOS apps using ethOS as reference
why: forking may bring more headache than it solves, easier to add code than remove it, the light client implementation for starknet may not be similar (geth android lib vs. porting beerus rust crate)
Starknet Phone Preface
Category: MVP
Exploration Hypothesis
The current mobile UX is very bad. The way to approve it is to implement a light client and wallet at the OS level.
Scope:
options for development:
options may not be all that different, since the implementation is done with apps, rather than integrated directly in the OS. So we can potentially create light client app and integrate into either OS.
Fork grapheneOS, using ethOS implementation as a reference.
Fork ethOS and swap to support Starknet
Simply implement light client + wallet + injected browser on android directly
Important question: is the priority UX or security?
Chosen solution: Fork grapheneOS and add in starknetOS apps using ethOS as reference why: forking may bring more headache than it solves, easier to add code than remove it, the light client implementation for starknet may not be similar (geth android lib vs. porting beerus rust crate)
Project Continuation
DP from SNF