My startup basically broke up when my business partner decided to make an app while I was off consulting to keep money in my pocket.
As part of the app development process I said I could devote 2 hours a night to help out the developers working on the app.
Because of some server issues and a friend on whose server farm things were hosted being on vacation I ended up using 20+ hours the first week.
In about the second week the app developer started complaining that he couldn't get the api I had made to work (which to be fair it had some warts hoo boy), he could do the initial PUT which would return an id for the thing that was PUT but he couldn't GET that item later.
So I sent him 2 example curl snippets to show it worked, it just basically read in a very small json file, less than 1kb and sent it off got an id back, the second snippet did a GET of the id returned.
His reply - the curl example works, but I'm not a curl expert, it would really help me out if you download the framework/tool I'm using (which I was unfamiliar with) and figure out what's wrong. I actually found I was incapable of answering him without swearing, so I didn't.
In conclusion: I believe this article may have been written by a significantly younger person than me.
Developing in Android is like navigating where the streets have no name...and if you ask for directions to google you are slut shamed (pardon my usage of the term but since the article has profanity already ;-) ).
> Fuck you for providing such a great security to my app that any fucking idiot can decompile it and do whatever he wants.
I haven't developed for Android in a while, but this passage deserves some counterweight. Security through obscurity is not (really) security, and there is nothing wrong with users having some control and insight in the software they are running on their own devices.
What excites me most about the librem project is that I can hopefully put an app together with just a c file and a make file, as with regular gtk. The android development process is the most horrendous one I've ever encountered, making simple things require 3 xml files and half a dozen classes and growing exponentially from there.
7 comments
[ 3.1 ms ] story [ 27.7 ms ] threadhttps://stackoverflow.com/questions/17421104/android-studio-...
As part of the app development process I said I could devote 2 hours a night to help out the developers working on the app.
Because of some server issues and a friend on whose server farm things were hosted being on vacation I ended up using 20+ hours the first week.
In about the second week the app developer started complaining that he couldn't get the api I had made to work (which to be fair it had some warts hoo boy), he could do the initial PUT which would return an id for the thing that was PUT but he couldn't GET that item later.
So I sent him 2 example curl snippets to show it worked, it just basically read in a very small json file, less than 1kb and sent it off got an id back, the second snippet did a GET of the id returned.
His reply - the curl example works, but I'm not a curl expert, it would really help me out if you download the framework/tool I'm using (which I was unfamiliar with) and figure out what's wrong. I actually found I was incapable of answering him without swearing, so I didn't.
In conclusion: I believe this article may have been written by a significantly younger person than me.
on edit: clarified the curl snippets.
I haven't developed for Android in a while, but this passage deserves some counterweight. Security through obscurity is not (really) security, and there is nothing wrong with users having some control and insight in the software they are running on their own devices.