1. The scripts you write calls directly to Java methods, so is much easier to access Android API calls
2. PHONK is not only a framework, is a development environment that lives in your phone, so no needs to install npm or any other tool in your computer. You can write scripts directly on the phone, or using a remote Web Editor that is hosted by the device itself
3. The PHONK API is tailored for quick prototyping, making and exploration. I invite you to have a look to the built-int examples and see how easy is to access sensor data, communicate with Bluetooth Low Energy, add maps or create interactive sound to name a few things!
Thats definitely the cool part. With a debugger I can definitely see some good use cases for this.
What debugging workflow do you think would be important?
so for example you can write the following to include a button
ui.addButton('Click me', 0.1, 0.1, 0.8, 0.2)
That's quite fast to do, but on the other side it makes it a bit cumbersome if your UI is complex and you need to support lots of screen sizes.The good thing is that PHONK is quite easy to extend and virtually you could expose any Android API to the Javascript engine.
Packaging a PHONK script is possible but I haven't had much time yet to write a guide. I you want, you can follow this issue and upvote it if you think is worth it to have a guide! https://github.com/victordiaz/phonk/issues/9
Sometimes if you write some code that makes PHONK unhappy, the app will freeze / crash but that's all :)