Front End UI Investigation #800
Replies: 4 comments 5 replies
-
It looks beautiful 🤩 |
Beta Was this translation helpful? Give feedback.
-
I think those both look fantastic. With some very quick and dirty Photoshopping, I am wondering what your thoughts on the following 1.5 concepts. On the Overview page, on the left, there's the "Species Detected Today" link. Right now, it just lists the species detected as a table. I think it would be super nice if there was an option to make it a gallery. This could be as simple as just a table with a single picture in one cell, the common name in the cell below and the scientific name in the cell below that. The table's columns could be dynamic or fixed. My thought is that a gallery with pictures would be much more engaging to someone like myself who doesn't know what many of the birds look like. On a slightly different note and building on what was posted above... I feel the initial presentation of a more compact form may be helpful. The spectrograms are great but they dilute the flow of species. If each of the cards could expand when tapped and then show the corresponding spectrogram, that would nice. Most important to me would be an option to shown only the unique species and not the individual detections of the same species. (Yeah, I know the graphic I cobbled together doesn't show this.) The card associates the time and the percentage together as well as having the playback control in the same area. Once again, I think this project is amazing and thank you for everything that you do! |
Beta Was this translation helpful? Give feedback.
-
Love the idea and looks awesome :). I'm along to help you flesh it out and develop. Can I suggest we use Limonade to power the API? just so it's super lightweight and looks after handling the URLs and JSON output Have the API completely separate to the existing code (so we end up duplicating functionality and can run both the old and new UI side by side) Have the API directory like this Each of the API endpoints in their own file... we probably won't have too many, likely settings, services and detections (holds responses for everything from latest detections, species etc) Then more or less describe the API endpoints like this
|
Beta Was this translation helpful? Give feedback.
-
I have finally added the repos here on GitHub for this. The first is a fork of this repo that adds the necessary api paths to enable the frontend UI. The other repo is the UI itself. This is really more of a proof of concept than anything but the basics work for the overview page and the search page. The front end is in react/typescript using Vite so you'll need node to do any development/building of the UI. I'm glad to see there's interest on this and look forward to moving this forward to a more complete package! https://github.com/tcatkins99/BirdNET-Pi |
Beta Was this translation helpful? Give feedback.
-
Hey all. I've been following this project for a while and finally got it setup on a Pi over the weekend.
Since I can't help myself, I decided to start tinkering with things and figured I'd have a go at a revamped UI. My background is React so of course I started there!
My idea is to add an "api" of sorts that just serves up JSON to the front end and React handles the rest. I'm not at all a PHP guru but I have at least gotten enough hacked together to serve up JSON in order to create the below basic overview page. It's not even close to feature complete but I just wanted to see if I could at least prove that it could be done.
Anyway, if there is interest in this I'll continue forward on it and setup a fork for this and hopefully others will contribute.
Beta Was this translation helpful? Give feedback.
All reactions