When showing information in your UI, you often want to refresh the data when something changes to provided the most accurate information to the user. The most efficient way to do this is by having the server push new data to the WebUI by using Server Sent Events, WebSockets or a similar technique. A lot of APIs however do not offer this, but only support the basic HTTP operations. This means that if you want to refresh the data the only choice you have is to poll the server. This happened to me recently, we wanted to auto-refresh the data on our pages, but our backend application only supports simple GETs. While in the long term we should definitely change this to support sending data from the server, but for now this is what we have. In this blog post I will discuss my solution to doing this.
When re-working an existing application I was wondering whether I should continue using Angular Material Design or just switch to Bootstrap. While I have used Bootstrap in the past when working with normal HTML web pages, I never used Material Design. The only experience I had was how the application looked like, and that was horrible. My first reaction was to just start over and use Bootstrap instead of Material Design, but the decision was not that easy as I hoped it would. In this blog post I will compare Material Design and Bootstrap.
As mentioned in the previous blog post, I will continue with my remarks about some Angular 4 design choices, similar to what I did in the previous one. The course I followed was very in-depth about Angular 4, but there may still be things I do not know. I am not an expert in Angular 4, and my real life experience with Angular is very limited. I am aware that this may influence my opinion and cause me to dislike certain choices while better ways to do it exist. I am open to this, and please let me know if you have any comments or advise for me.