![]() ![]() But as already said: we want to go the full way and deliver an application that people are able to love. Needless to say that this is a very demanding and time-consuming endeavour. Therefore, although we a had a wonderfully working user interface and design with our Mac app, we decided to step back and find out what a great Windows app should look and feel like. We thought that Windows users deserved better. That's why we ended up with 216,724 lines of C# code and a 100% native WPF application.Īlso, we didn't want to just "clone" Tower for Mac. We wanted a 100% native experience with Tower for Windows, from the app's performance to its user interface and feature set. ![]() Frameworks like Electron might have produced a result faster - but this wasn't what we wanted. Having written Tower for Mac with only native technologies (Objective-C for that matter), we were long arguing over how to approach a Windows version. As a Windows user, you might have an obvious question for us: "Why (the hell) did you let us suffer for so long?" Our answer is rather simple, though: "We wanted to get it right." ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |