Add README.md to get starting users up and running

holtkamp commented 5 years ago

Seems like the minimal to do to get developers up and running. It is quite a big puzzle now...

Also the link to the "Android Emulator" section is broken.

For some reason https://doc.bunq.com/#android-emulator redirects to https://doc.bunq.com/#/android-emulator

OGKevin commented 5 years ago

There should be ONE entry point to reduce overhead. Right now there is doc and 4 sdk readme's.... its just too much to properly maintain. imho those 4 readmes for the SDK's should also go 🙄.

So, i would suggest create a PR on bunq/doc and add the explanation you're missing there. All info should be on doc.

And then the readme's should just say read on doc.

For the broken doc links, please create issue on bunq/doc as well.

holtkamp commented 5 years ago

Uhm... I would "assume" a Bunq member would do that...

Posted on "Together" a few times, which seems to be ignored...

OGKevin commented 5 years ago

Uhm... I would "assume" a Bunq member would do that...

i don't understand this one.

Posted on "Together" a few times, which seems to be ignored...

🤦‍♂️ Do you have an example so i can double check ?

holtkamp commented 5 years ago

i don't understand this one.

Aah, sorry. I was just a bit frustrated with not being able to get a developer key / the sandbox app working by following the documentation. I should not have created an issue in a rush, my apologies...

What I meant was that I would assume that the "task" to "improve the documentation for the community", is not a task for the community itself but for a Bunq member/employee. I just reported that it is all quite confusing how it all works. Documentation is/seems scattered and outdated.

I will try to collect points for improvement and report them at https://github.com/bunq/doc

Do you have an example so i can double check ?

For example:

bunq / tinker_php

Add README.md to get starting users up and running #30