@mul1sh what do you think about having both codebases in the same repo?
We would have to rename them, e.g. /videoDAC/android/android could become /videoDAC/android/pay-to-play alongside videoDAC/android/livestream-to-earn
I imagine that it could allow them to integrate more effectively, and indeed to share code.
For example, the "lock screen" button for the Consumer app could also be very useful in the Publisher app - to avoid fat-fingers killing the livestream for all the Consumers. Perhaps this becomes videoDAC/android/ui-utils.
Also, the code to integrate with Connext (or indeed any future payment protocol, like Orchid) could be shared very elegantly across both apps, like videoDAC/android/integrations/orchidprotocol and used by both app templates.
There would also be a job to do to rationalise the documentation, but that's the final polish.
Also, what do you guys think about closing the source of android repo, while we polish it up @psudoanon?
@mul1sh what do you think about having both codebases in the same repo?
We would have to rename them, e.g.
/videoDAC/android/androidcould become/videoDAC/android/pay-to-playalongsidevideoDAC/android/livestream-to-earnI imagine that it could allow them to integrate more effectively, and indeed to share code.
For example, the "lock screen" button for the Consumer app could also be very useful in the Publisher app - to avoid fat-fingers killing the livestream for all the Consumers. Perhaps this becomes
videoDAC/android/ui-utils.Also, the code to integrate with Connext (or indeed any future payment protocol, like Orchid) could be shared very elegantly across both apps, like
videoDAC/android/integrations/orchidprotocoland used by both app templates.There would also be a job to do to rationalise the documentation, but that's the final polish.
Also, what do you guys think about closing the source of
androidrepo, while we polish it up @psudoanon?