-
Notifications
You must be signed in to change notification settings - Fork 2
Evaluation of tools Milestone 4
On backend side we used Spring Framework with Java. Throughout the development we used free student version of IntelliJ. It has many different tools to provide us a fast development environment. We are glad for this choice. We used Postman and Swagger UI to test out API. Both of them are easy to use.
For deployment we are using AWS EC2. We created our CI/CD pipeline with Travis. Our database lives in a database instance on AWS RDS. We created an instance of Postgresql database and currently using it. All services of Amazon have a good documentation and performance.
On front-end we use React to create a dazzling web application. For UI & Styling we use ant.design components. For requests we use axios, for routing we use react-router. There is an ongoing discussion about using Redux for state management, we are still not sure about the gains we try to have will outweigh the cost of complexity just yet.
Our tooling on front-end does not fail to satisfy at the moment, we are lucky to have considerable developer experience on our team so everything is going well, design and tooling-wise.
We are using Android Studio to write our app. After the first milestone, we have learned more about Android Studio and I think we can use it more efficiently now. We were adding log messages for debugging before the previous milestone. Lately, we have learned about the debug tool in Android Studio and we started to use it. It enables us to see the values of the variables and it is faster to use than adding log messages. I believe we started to use Android Studio better now.
I think we are continuously improving on using Github more efficiently. After the previous milestone, we started to write longer commit messages and longer issue descriptions. We also have started to use project feature in Github. We created a project for Android Kereviz and we are adding our issues to there so it is easier to follow the process. One matter that I think we can improve is the code reviews that we are doing. Because we are usually getting together and writing the code together, we ask our questions about the code face to face and solve them together. When someone has a pull request and we are reviewing it, we usually don't make about the code as we have already seen the code when it is being written. Currently, this doesn't create any problem for us but I don't think it is a very good habit to have.
We have chosen Java language to implement our Android project. We are generally happy about Java but we have only one problem with it. We usually have synchronization problems when we are sending a request to the backend. We heard that this is not a problem in Kotlin but we couldn't solve this problem with Java.