Splitter app build with Svelte

What are you most proud of, and what would you do differently next time?

I'm most proud of the efficiency and elegance of the code I produced while working with Svelte. Svelte's declarative approach allowed me to write concise and readable code, resulting in faster development and smoother user experiences. However, looking back, I realize that I could have spent more time initially planning the project's architecture and component structure. Next time, I would focus on creating a more detailed plan before diving into development to ensure a more organized and scalable codebase.

What challenges did you encounter, and how did you overcome them?

While working with Svelte, I encountered challenges related to understanding the reactive nature of the framework and managing component state effectively. Initially, grasping the concept of reactivity and how it differs from other frontend frameworks took some time. To overcome this challenge, I devoted extra effort to studying Svelte's documentation and experimenting with simple examples to solidify my understanding.

What specific areas of your project would you like help with?

I'm seeking feedback specifically related to the solution I've implemented in Svelte, including an evaluation of my strengths and areas for improvement. I'm particularly interested in understanding where my implementation excels and where it falls short in terms of performance, maintainability, and user experience. Additionally, insights into any overlooked features or alternative approaches that could enhance the project's overall quality would be greatly appreciated.