How to create a plant identification app for ubuntu touch?
-
I fed it images straight from the camera and it worked just fine. I did not crop or edit in any way.
-
@moem yeah those are jpeg. But you might have pngs in the gallery. Although maybe it would be unusual.
-
@s710 said in How to create a plant identification app for ubuntu touch?:
yeah those are jpeg.
That's right. Sorry, I was not responding directly to your plan to add some kind of .png support... just reporting my workflow, out of general enthousiasm!
-
@s710 Sorry for appreciating your efforts very late but thank you. I will submit a few more images of plants by tomorrow.
-
@s710 awesome work. Copy paste to the api key doesn't work for me but copy paste is hit and miss in UT anyway. Btw i now realize I had this warning during my conversation with them: "Making users signup to the API individually is against our term of use.
You can find the agreement here: https://my.plantnet.org/documents/agreement_PlantNet_API_english_v4.pdf"
So this hardly can be a long term solution. I gave them the repo address just now, and even though i didn't imply it was already published, they'll find out. -
@emphrath said in How to create a plant identification app for ubuntu touch?:
@s710 awesome work. Copy paste to the api key doesn't work for me but copy paste is hit and miss in UT anyway. Btw i now realize I had this warning during my conversation with them: "Making users signup to the API individually is against our term of use.
You can find the agreement here: https://my.plantnet.org/documents/agreement_PlantNet_API_english_v4.pdf"
So this hardly can be a long term solution. I gave them the repo address just now, and even though i didn't imply it was already published, they'll find out.Hmm okay well. Then I am wondering how this could work out at all
-
@s710 i'm confident they'll extend api rights for UT.
-
@emphrath I don't see how this could be done in a secure way. They could supply a dedicated API-Key with increased usage limits, however it would be impossible to ship the key within the app without the possibility to reverse engineer the key and use elsewhere. Of course, depends if someone is actually willing to reverse engineer, and someone actually looking for an API-Key for Pl@ntNet. Just trying to say that shipping credentials is never a good idea.
-
@s710 well, they could also increase quota for one specific existing api key - in that case, everything happens on their side
-
@emphrath said in How to create a plant identification app for ubuntu touch?:
@s710 well, they could also increase quota for one specific existing api key - in that case, everything happens on their side
Same difference, that one API key would need to be distributed somehow.
-
@arubislander Well how do they make their own android app work then ? I don't get it.
-
@emphrath said in How to create a plant identification app for ubuntu touch?:
@arubislander Well how do they make their own android app work then ? I don't get it.
Yeah well, maybe they're using non-public APIs. Those, of course, can also be reverse engineered from the binary.
I am no expert in reverse engineering, but I was told that virtually anything can be reverse engineered with enough efforts. For example, someone reverse engineered the HTTP APIs used by the Bird Scooter app (which, btw, enabled me to make a scooter app).Unless you're using a dedicated authentication (user must login within the app), there is virtually no way of publishing something secure, you simply cannot ship credentials/hidden stuff. Of course, this is from a pure security perspective. The owner might still decide to ship apps like this and rely on no one caring about reverse engineering, which might be an acceptable risk.
In the end, it completely depends on what Pl@ntNet wants to do. I just wanted to point out that if I was given a dedicated API key, and Pl@nNet would increase limits for this single key, I would need to ship it within the app, which would be insecure per design. Of course, I can try to occlude it as best as I can, but it won't be bullet proof. If Pl@ntNet accepts this approach, I don't see any real issues, since I guess that not so many people would be that eager to get into possession of a Pl@ntNet API-key with increased limits so that they would actually take the efforts of reverse engineering it out of my app.
-
I have given this a go just now and really like it and the way it has come into being from initial idea to working app all form within the Community. Great work from all involved. This is really what the UBports Community does well. One small idea if the link to the my.plant.org website could be a direct link from settings (if possible) it would make things smoother.
If any further help with api keys or/and gaurantee of or licensing usage and such become needed let me know and I will see what can be done. -
@s710 You should probably just make it such that the user would have to acquire their own API key, and provide a UI for entering it in your app. Otherwise, do you plan to pay the fees for going over the number of requests, or even paying €1000/yr?
The contract PDF you linked to is very much oriented toward scientific organizations building applications for research, and doesn't seem to be oriented toward people who want to occasionally query Pl@ntNet for what plant they find while out on a walk.
-
@dobey It is exactly that at the moment. The matter at hand is wether it can last
-
@dobey said in How to create a plant identification app for ubuntu touch?:
@s710 You should probably just make it such that the user would have to acquire their own API key, and provide a UI for entering it in your app. Otherwise, do you plan to pay the fees for going over the number of requests, or even paying €1000/yr?
The contract PDF you linked to is very much oriented toward scientific organizations building applications for research, and doesn't seem to be oriented toward people who want to occasionally query Pl@ntNet for what plant they find while out on a walk.
The app works like this. The user needs to provide the key.
I was under the assumption that they know we make an app since they do not provide one for UT, and they are okay with it. So they should be aware of the fact that there are only to ways it can work: 1) per user developer key 2) dedicated shipped key with special limits. -
@s710 Got some news from the team at PlantNET (which as it seems just came out of attending a conference about open source software ^^):
" Hi Georges,
Great work! I've forwarded the repo to the team!
Let us know if you need anything from us.
Best"
So, maybe @Lakotaubp you want to take it from there ? I guess we could also wait for their feedback.
-
@emphrath I tend to think at present lets see if they come back with anything as your line of contact is obviously working well. If we hit problems with usage or they get back to you with an issue you can't sort from an app point of view let me know. Probably best by PM so as not to clog this thread with stuff and thanks again to all involved great work.
-
@lakotaubp you are right.
-
If you do need to go to a single key - it might be good to use compiled qt in the build that goes to the store, so the program is within a binary and the plain qml not stored anywhere. Let me know if you need to do that and I can help.
