How to create a plant identification app for ubuntu touch?
-
@s710 Wow, awesome. I guess it won't be using ReactJS then ? Do you think I should let them know sth is being worked on native-wise and pass along your suggestion of extended API rights ?
-
@emphrath said in How to create a plant identification app for ubuntu touch?:
@s710 Wow, awesome. I guess it won't be using ReactJS then ? Do you think I should let them know sth is being worked on native-wise and pass along your suggestion of extended API rights ?
Correct. I have a working prototype, which is able to pick images from your camera or gallery, and then use their API to identify it. Currently I am working on displaying the results / designing the UI for the results.
As I don't have time to work on it today, I would say by the end of tomorrow I will be able to provide screenshots of the app, which you could then send them if you want.Basically, there are no technical issues or blockers here, its just a matter of time to get the UI nice and polished now.
-
Teaser:
-
@s710 omg that's a dream come true ^^ you're the man. Nice interior plant btw. Alright I'll let you know how and when they're willing to help.
-
@emphrath Some more screenshots:
-
@emphrath You can show them those screenshots if you want. The app is coming closer to being finished. The screenshots show the workflow of starting with an empty app, adding a picture for identification, receiving the result, saving the result, and then displaying the plant in the overview of already identified plants. I have omitted screenshots for selecting a picture from camera/gallery.
But I guess the order of images got messed up, I'll try to edit the post to correct the order.Open points:
- Language detection for localized identification result (plant "common names" in local language)
- Automatic resizing of input images (API requires a certain max size)
- Add settings page for API-Key configuration & setup instructions
- Make the app icon
I guess I will be able to finish the app during next week, and publish it to the store. I can also not publish to the store and only upload to github, in case Pl@ntNet is interested in taking over the app. The app is written in maybe 50% C++ and 50% QML. Storage layer & network functionality is implemented in C++, display stuff is in QML.
-
This post is deleted! -
@s710 Thanks for your effort. You can open the source code in gitlab/github to contributions for your excellent newborn application. I know a few unique species of plants and trees which I will contribute to your application for sure.
-
@s710 you rock. Period. I'll submit your screenshots and questions to the team at plantnet.
-
I would lovesuch an app! This is really one if the few things I've always missed as a UT-user. What I did is using the web-version of pl@nt.net (https://identify.plantnet.org/) and then I created an app with webber. It's slow, and I don't know what functions I am missing compared to Android and iphone. Anyway, still faster and more accurate than me identifying plants by looking it up in a book
Looking forward to a real UT solution
-
@taiga-woods oh yeah, the webber solution was also the cross I had to bear ^^
-
Thanks guys for the feedback.
Please keep in mind that I’m basically just implementing what was said in the initial post. This means that I’m no Pl@ntNet user, and I don’t know their iPhone app and their other features.
Looking at what the my.pl@ntnet API seems to expose, this especially means it will not be possible to submit own categorisations. IF their API allows it, of course I’m gonna happily add it to my app. But upon first look, it only allows to identify plants by pictures.Also, the UT user will have to sign up as developer in order to get a key, which is needed to use the API. But let’s see what @emphrath can negotiate
Thanks for doing the communication. -
@s710 If what you are saying is true then try opening your half-developed application on github for contributions. These contributions might solve any of the issues you are struggling to fix. Even I will try looking into it.
-
@quilty-weavy There are no issues I am struggling with. It all depends on what the service of Pl@ntNet is offering. And this can only be influenced by Pl@ntNet, and not by external app developers (me).
As per https://my.plantnet.org/usage, their service only allows to submit images to get a plant identification back.
There is no feature in their public service which allows to submit own identifications back to Pl@ntNet.As stated on the linked website, one should use their official apps (iPhone, Android) instead to contribute and submit identifications. Of course this means that there must be a service to submit own identifications somewhere, but it is just not available to the publicity / external app developers.
As @Emphrath is already in contact with Pl@ntNet, and they seem to be aware of us making an app for UT, and they know that no offical apps for UT exist, maybe they will be opening the service to submit identifications to me/us, so I can integrate it into the app. But thats completely out of our hands.
Hope I explained it well enough.
-
@s710 hey there ! They said: "maybe we can increase the quota to sth later on when the app is finished" this is encouraging. They also are asking for the repo - could you provide that ?
-
-
@quilty-weavy Why do you want to change the UI or fix bugs? I mean I am working on the app, and of course I will fix bugs when they are found
Do you have any comments or requests for improvements? Just let me know and I will take them into account.
I will publish the code to github tomorrow or on wednesday, not going to find time for it today.
-
@s710 you can publish the code whenever you want. It is your decision, because it is your app.
-
@s710 some news: there should be a clear mention somewhere that this is not an official Pl@ntnet app. And I believe you don't have to delay the publishing to the store when you're done, because:
"If you mention that this is NOT an official Pl@ntNet app, then we are good.
Publishing the app as open source should be mandatory for the quota to be increased." So as long as they've got the repo address for them to browse, I don't think that they care too much about how and when it's published. -
Alright, so here is the first version:
https://open-store.io/app/plants.s710
Let me know what you think of it, and if it works for you.
