Kahla.App
Kahla.App copied to clipboard
Discussion: the future of kahla
Below are my suggestion, order represents priority. Fell free to express your opinion.
- Writing test before implement.
- Replace web socket with other protocols. It's hard to tell which temp message is sent or not in the current design.
- Support end-to-end encryption. Almost all the apps in this page offering E2E encryption.
- Use a CSS framework.
- Discard electron or create a separate project. Electron app shouldn't be a 100MB broken web page.
- Refactoring with react.
- Support voice and video call.
- Provide .onion domain.
- Replace non-FOSS
Wow. That gonna be hard work.
Have you considered web assembly?
And what is .onion
domain?
If we discard electron, how shall we face desktop environments whose browser is f**king 360 browser or QQ browser?
@xxyzz
As for refactoring to react,
You need to understand that we have spent years on Anuglar. And Angular works fine with electron, PWA, service-worker, web push and typescript.
But for react: none of our team once learnt it before. All of us need to re-learn everything about it. And try to implement PWA on it. That gonna be very hard work.
Giving up our thousands of lines of code and refactor it with another technology costs us something. You need to provider two lists before really decide it:
- What we will get if we refactor.
- What dose it cost if we refactor.
And then we will try to balance if it is worth to spend it on the second list and get benefits from the first list.
For now, I think we should focus on reflacting existing code and add features (voice call + E2E)
@Xiangrui2019 why edit it?