3 ms·

Can't emphasize this stuff enough. What problems does it solve for the user? It's described in very general terms, which I'm going to assume is because it's a g

by sedev 12y ago

Can't emphasize this stuff enough. What problems does it solve for the user? It's described in very general terms, which I'm going to assume is because it's a general-purpose tool that can solve many problems. Show some of them! Are they problems people already solve in a different way? Show why yours is better.

sdegutis 12y ago
Thanks to both of you. I've updated the website now to include some things that help clarify some example use-cases. I hope it helps?
- gglanzani 12y ago
  First and foremost: great job shipping it! Regarding your question: I'd still love one (captivating) example, one 10s video to "pull me in" and convince me to install it. Looking forward to it.
  - sdegutis 12y ago
    Thanks! I added some screenshots. They're more easily seen in the Github readme than on the website. (I really ought to change to a different Github-Pages theme.)
- vtail 12y ago
  Thanks - it does help. So now I have a better understanding what it does - if I were to express my understanding in a single sentence, it would be something like "Mjolnir allows you to script Apple mouse events or system dialogs in Lua and assign them to a hotkey - no need to use Apple C API". Again, if you target Mac power users (which is the right market you should probably target - much bigger than just developers), I would emphasize higher-level stuff you can do with Mjolnir and ease of use comparing to AppleScript. For some inspiration, go to App Store and search for "Automator" - you'll see several bundles that help people automate programs like Adobe Illustrator, etc. Just my 2 cents. Good luck!
  - vtail 12y ago
    Here is another idea/fun experiment: try to express your idea in: - 5 words - 1 sentence - 1 paragraph - 3 paragraphs Adding constraints like that really help you focus on what's important. For example, does "Lightweight" section belong to the introduction, or is it an implementation detail? Should you move screenshots up on the page above the "fold line"? etc. etc.

by sedev 12y ago

sdegutis 12y ago

Thanks to both of you. I've updated the website now to include some things that help clarify some example use-cases. I hope it helps?

gglanzani 12y ago
First and foremost: great job shipping it! Regarding your question: I'd still love one (captivating) example, one 10s video to "pull me in" and convince me to install it. Looking forward to it.
- sdegutis 12y ago
  Thanks! I added some screenshots. They're more easily seen in the Github readme than on the website. (I really ought to change to a different Github-Pages theme.)
vtail 12y ago
Thanks - it does help. So now I have a better understanding what it does - if I were to express my understanding in a single sentence, it would be something like "Mjolnir allows you to script Apple mouse events or system dialogs in Lua and assign them to a hotkey - no need to use Apple C API". Again, if you target Mac power users (which is the right market you should probably target - much bigger than just developers), I would emphasize higher-level stuff you can do with Mjolnir and ease of use comparing to AppleScript. For some inspiration, go to App Store and search for "Automator" - you'll see several bundles that help people automate programs like Adobe Illustrator, etc. Just my 2 cents. Good luck!
- vtail 12y ago
  Here is another idea/fun experiment: try to express your idea in: - 5 words - 1 sentence - 1 paragraph - 3 paragraphs Adding constraints like that really help you focus on what's important. For example, does "Lightweight" section belong to the introduction, or is it an implementation detail? Should you move screenshots up on the page above the "fold line"? etc. etc.