I want to learn GO by building a small chat app with Go backend, Websocket or gRPC (in consideration) and React + Material UI or Flutter (in cosideration) frontend.

Why? My research suggested that Go is best for web application backend and microservices. The frontend is hence needed and a good way to transfer data is also very important.

All proofs of concept have been verified and the app is ready to finalize. However, the next step is about UI design, which I, as a handsome technical boy who has very low tolerance for inelegant, find it quite troublesome since I want to make it beautiful but at the same time have no idea how it can be done. Hence I decided to spend some more time playing with Flutter and making a new personal blog post to learn about design before continuing to play with this.

• Practical and complete understanding of Mutex.
• First experience with router and navigator.
• Basics of the incredibly powerful gRPC.
• Basics of Go and concurrency with Go.
• Basics of the absolutely stunning Flutter.
• Using Google Firebase for UI hosting.
• Database workflow and patterns in Go.
• Generic understanding of middlewares.
• Dockerization of server and client.
• Deployment to cloud.

• GRPC doesn't work well for WEB -> gRPC-Web.
• Server streaming not working for grpc/grpc_web.dart -> NEVER end stream function.
• An absolutely free (no hidden costs or registration) simple CPU server for the backend is no where to be found :'(.

• Auto-generate models in Go and JS -> the pain of rewriting the same stuff in the client-side -> gRPC + protobuf 3.
• Play with Flutter Web -> incredible but some problems with releasing.
• Test if Go can publish a web UI -> by http.FileServer.
• Test websocket communication -> by gorilla/websocket. (outdated)
• Use a docker database to persist data.
• Build a non-compromised chat UI.
• Implement all key features.
• Deploy to a docker image.
• Deploy to Google Cloud.