Update README.md

README.md

@@ -64,17 +64,41 @@ ___
 
 Please submit the answers to the following questions in the README.md file
 
-* How long did you spend on the task?
-* Rate from 0-10, how would you assess the complexity of the task? _0 - very trivial_, _10 -
-  extremely complex_
-* If you had more time (or if you were doing it in production) what would you have changed/improved?
-* Which parts of the code would you like to highlight?
-* In your opinion, which Google library was the best addition to the Android Dev world in the last
-  years?
+* _How long did you spend on the task?_
+
+  ~16h
+* _Rate from 0-10, how would you assess the complexity of the task? _0 - very trivial_, _10 -
+  extremely complex__
+
+  Difficulty - 2
+
+  Complexity - 7
+* _If you had more time (or if you were doing it in production) what would you have
+  changed/improved?_
+    * I would remove hardcoded text values.
+    * I would add more tests.
+    * Improve `Cache`, to use also Room as cache e.g. for Airports, instead of memory cache. Right
+      there is no refresh mechanism for cache.
+    * Improve sort and group logic for Stations
+    * Of course UI, it can be more adaptive. Split UI implementation into smaller reusable
+      Composables.
+* _Which parts of the code would you like to highlight?_
+    * App architecture - multimodularity, separation of concerns, etc.
+* _In your opinion, which Google library was the best addition to the Android Dev world in the last
+  years?_
+    * In my opinion, Jetpack Compose has been the most impactful and transformative Google library
+      added to Android development in recent years.
 
 > If you have the need to comment the provided task, we would love to hear that from you 🙂  
-> ...  
-> ...
+> 
+> The idea behind the task was quite straightforward, and I didn’t encounter any major difficulties
+> during the implementation.
+> However, given the limited time, I had to make some compromises, and the current solution is
+> certainly not perfect — a keen eye might spot some flaws. That said, I hope to demonstrate that the
+> application is well thought out in terms of its architecture, which was my main focus.
+> Each area — UI, Domain, and Model — has its own dedicated space with appropriate layers of
+> abstraction and dependency injection. In short, it’s a compact example of applying SOLID principles
+> in practice.
 
 ### Time frame