Thanks for the ideas @gbathree! I’ve been using the Planting quick form a bunch myself this month (Happy Spring! 
) and have been thinking about lots of next steps too. 
I’ve also been using it in combination with the (alpha) Crop Plan module - it’s definitely too tedious for general use, but it’s really nice to have the visualization of the season. The Planting quick form is loosely tied in to the process: the Crop Plan offers a link to it so you can create the Plant asset + Seeding/Transplant logs, then brings you back to fill in Plan-specific details (days to transplant/maturity + days of harvest). Very tedious still, but serves to inspire lots of ideas while using it! I might start a thread to organize them soon.
As for your feedback, here are some thoughts…
Maybe you noticed this already, but the Planting quick form does offer the ability to modify the Plant asset name before it’s saved. Here is what it looks like:
I often find myself overriding that and removing the location name too (like you describe), because I don’t need to differentiate the same plant type across multiple locations. Some people do, though, which is why the default is [Season] [Location] [Crop].
I’m not sure we should change that, BUT I have definitely thought about making that default pattern configurable per instance. Then you would be able to set it to something like [Season] [Crop] (omitting [Location]), and you wouldn’t need to manually override it each time.
Do you think that would be enough to meet your needs?
Agree! I actually had this same thought the other day. We should absolutely implement this.
These are good ideas too. I’ve been wanting to overhauls the “autocomplete search” widget for a long time, so maybe we can take these into consideration at the same time. This probably deserves a dedicated topic.
The second idea (tacking on additional info in certain places) gets tricky because: what if it’s already included in the name? Then you end up with “2019 north field raspberries (north field)”.
If we take that idea to it’s logical conclusion, you start to ask if we should have asset names at all, or if they should be auto-generated based on attributes everywhere instead. But then we will have different users with different needs, and different contexts within a single farm, etc etc, and I think we come full circle back around to what we have now: a free form asset name field. 
Generally speaking, I do think it’s important to have as much information in the asset name as is necessary to identify it and distinguish it at a glance. So, if you have “Corn” in “North field” and “South field” during “2025” you really should name your plant assets “2025 North field Corn” and “2025 South field Corn”. Or if you plant 10 successions of Red lettuce, you should have “2025 Red lettuce succession 1”, “2025 Red lettuce succession 2”, “2025 Red lettuce succession 3”, etc (I’d love to see the Planting quick form support succession creation at some point… or maybe that’s a Crop plan feature 
).
It does mean that the standard lists (with “Name”, “Location”, and “Plant type” columns) become somewhat cluttered with duplicate info, but it’s hard for us to predict when that will be an issue. Side note: we’ve been talking about making the listing page columns more configurable, so you can show/hide certain ones in certain contexts. That might help with “duplicate info” in contexts where that’s an issue.
It feels to me like we can do a lot more with UI and quick form configurability to ease these pain points.