Odd to see one of the best native plant communicators referenced on HN but I'll use to opportunity to mention a side project I'd been delaying diving in for years and finally committed to recently if there are folks here who want to not only learn to identify crucial native flora (and fauna) but contribute to restoring local native plants that are critical to ecosystems.
So, mini show HN: <a href="https://indigene.app" rel="nofollow">https://indigene.app is a browser-only, offline & mobile-friendly, no account, no ads, open source tool to help you find native plants that would thrive exactly where you are. I've tried to make it as thoroughly sourced as possible but focus heavily on folks that have less experience with gardening and native plants in general.
I've been adding coverage to a handful of US and French ecoregions for now (what I know) and you can already do plant lookups by GPS, postal code, and ecoregion). The app will help you identify you spot, sun, soil, and specific ecosystem support goals (wildlife, birds, erosion or runoff control, growth) and offer a sortable list you can fine-tune with requirements (max height/width, no thorns, pet safe, spread, zero watering, etc.).
There's a lot more in there I've wanted for years like bloom windows, host species counts, dependent native wildlife, growth-over-time charts, propagation tips, and tons of sourced references that overlap with a lot of the resources Joey Santore and other native plant folks reference.
None of this replaces useful tools like iNaturalist whose excellent open API I use to show what native plants look like in Indigene, but hopefully it encourages folks who have the means and the time to start rebuilding local ecosystems we've neglected or actively destroyed.
PS: because I can't help it, the app has detailed release notes gendered from its changelog at <a href="https://indigene.app/release-notes/" rel="nofollow">https://indigene.app/release-notes/. It also takes privacy & safety very seriously: <a href="https://indigene.app/privacy" rel="nofollow">https://indigene.app/privacy
Wow, this is a lovely tool, and it's clearly built with a lot of your own knowledge! I'm in New England and this has some great recs for my land.
One slight piece of feedback: it's pretty clear a lot of the text was output of AI. IME (and just _my_ E, of course), this detracts somewhat from the authority of the page, as it makes it seem more like it just came from a conversation with Claude, rather than from your knowledge filtered through building an app. Might be worth doing a couple of passes to tighten up and human-ize it a bit :). (since it's open source, I suppose I could always PR myself if you'd be open to it)
Thank you, it’s very explicitly the result of a relatively tight but fast TDD development process with Opus (4.8 & 5 mostly), a lot of cross-referencing with established sources (see <a href="https://indigene.app/sources" rel="nofollow">https://indigene.app/sources), and my own 30 years of amateur gardening experience and roughly 10 years of Florida & PNW native planting & observation experience.
So I take this feedback to heart and just like with the (sourced & generated) French localization I’m working my way through validating everything. This is another benefit of the project being entirely public, you can see precisely in the repo what I did and didn’t think to do in order to ensure accuracy.
When it comes to prose & style, I’ve set some clear accessibility goals in the agent config, and I’ve rewritten some things but it can be hard to fight the needless verbosity of LLMs at times.
I would deeply appreciate if you took the time to send a PR for any kind of improvement or addition). Thanks in advance.
olivierlacan · · focus · HN ↗
So, mini show HN: <a href="https://indigene.app" rel="nofollow">https://indigene.app is a browser-only, offline & mobile-friendly, no account, no ads, open source tool to help you find native plants that would thrive exactly where you are. I've tried to make it as thoroughly sourced as possible but focus heavily on folks that have less experience with gardening and native plants in general.
I've been adding coverage to a handful of US and French ecoregions for now (what I know) and you can already do plant lookups by GPS, postal code, and ecoregion). The app will help you identify you spot, sun, soil, and specific ecosystem support goals (wildlife, birds, erosion or runoff control, growth) and offer a sortable list you can fine-tune with requirements (max height/width, no thorns, pet safe, spread, zero watering, etc.).
There's a lot more in there I've wanted for years like bloom windows, host species counts, dependent native wildlife, growth-over-time charts, propagation tips, and tons of sourced references that overlap with a lot of the resources Joey Santore and other native plant folks reference.
None of this replaces useful tools like iNaturalist whose excellent open API I use to show what native plants look like in Indigene, but hopefully it encourages folks who have the means and the time to start rebuilding local ecosystems we've neglected or actively destroyed.
PS: because I can't help it, the app has detailed release notes gendered from its changelog at <a href="https://indigene.app/release-notes/" rel="nofollow">https://indigene.app/release-notes/. It also takes privacy & safety very seriously: <a href="https://indigene.app/privacy" rel="nofollow">https://indigene.app/privacy
nja · · focus · HN ↗
One slight piece of feedback: it's pretty clear a lot of the text was output of AI. IME (and just _my_ E, of course), this detracts somewhat from the authority of the page, as it makes it seem more like it just came from a conversation with Claude, rather than from your knowledge filtered through building an app. Might be worth doing a couple of passes to tighten up and human-ize it a bit :). (since it's open source, I suppose I could always PR myself if you'd be open to it)
olivierlacan · · focus · HN ↗
So I take this feedback to heart and just like with the (sourced & generated) French localization I’m working my way through validating everything. This is another benefit of the project being entirely public, you can see precisely in the repo what I did and didn’t think to do in order to ensure accuracy.
When it comes to prose & style, I’ve set some clear accessibility goals in the agent config, and I’ve rewritten some things but it can be hard to fight the needless verbosity of LLMs at times.
I would deeply appreciate if you took the time to send a PR for any kind of improvement or addition). Thanks in advance.