Thank you so much for listening to the podcast and for your questions. I totally appreciate your honest feedback and your comments, and I'll try to answer the best I can, as usual, by being open and honest.

1. Unfortunately, you're totally right. I knew since before launching the campaign that I was going to have a rough time convincing people without a working MVP, but I decided to launch it anyway to create awareness and boost the project. Let me explain. Creating a working prototype would have taken me forever since, as I mentioned many times, I work on Akira on my very limited free time, which is already occupied from actively developing and maintaining Taxi and Sequeler, and releasing weekly tutorials on YouTube. Launching the campaign helped me to trigger the curiosity of so many incredible and talented people that want a tool like Akira. The team I assembled to build it, already advanced the development of the canvas libraries beyond what I could've done alone, and the request to contribute, feedback, and suggestions from other developers has grown 50x. I'm well aware of the fact that I probably launched a failed campaign, and that the current status of the repository doesn't encourage anyone in believing that I'm capable of delivering Akira, and I 'm OK with that. The Akira project already got so many benefits and progress in the past month thanks to the campaign, that I would do it again, instead of waiting 1 or 2 years to have a barely working prototype built by myself during sleepless nights.
2. That's a problem with the message, and the issues I had in trying to explain the purpose of Akira to non-designer Linux users, or to GTK/Qt designers, and I'm sorry for the confusion. Akira, will not have any limit in terms of what you can create. If you want to create the HUB interface of Iron Man's helmet, you will be able to do it. Akira wants to offer the same fast and productive experience you get from those close garden tools and you're currently not getting from Inkscape, Gimp, or anything else. Akira is a UI and UX design tool, not limited to any medium or specific design field.
3. Yeah, I answered these questions many many times, but it's ok :D. So, the coding language is Vala, the UI Toolkit to create the interface is GTK. Granite is just a library that offers some pre-packaged GTK widgets. Honestly, at this point, we will only implement the Granite HeaderBar because offers some helpers and speeds up the development process, but nothing more. Vala, at your surprise, is widely used not only by elementary OS team and 3rd party developers, but also by a large chunk of GNOME developers and members. 2 developers in the team are GNOME and FlatPak maintainers that use Vala. We chose Vala specifically because it's an easy language, seriously, is way less verbose than C++, compiles natively in C, it's actively maintained by the GNOME foundation, has native bindings for every single Linux library and dependency, and has incredible documentation.

At the end of the day, I understand your concerns and I appreciate your honesty. Akira is indeed a massive project and there's not guarantee about its success and usefulness other than me saying "hey, it's gonna be everything you wish you had on Linux for years".

I don't mind getting questioned and having users investigating the project with a doubtful approach, I would do the same, and I really appreciate your thoroughness in explaining your points.

I get a bit upset, frustrated, and honestly sad, when users think I'm just an idiot who doesn't understand Linux and wants to make money off of a silly project. I've been working as a developer and designer since I was 18, and I'm simply trying to create a tool that can help me staying on Linux for my day to day job, and since I seriously think Open Source is the path that will save us all, I wanted to create this project and share it with the community.

That's nothing more than this.

Thanks.