I will add another post here once it's opened and available. Thanks for your interest :)
plantspack
I'll definitely consider this. It gets harder to maintain, the more users are joining, so I need to reconsider some of the aprooval flows, review flows etc. to make sure data-quality is at least stable and hopefully improving first. But UnifiedPush will indeed land in the backlog right below the basic F-Droid version
No valid reason tbh. I just forgot about it while building and now have tons of things to work on (also aside from the project). Will make sure to open the repo for contributions asap and notify everyone in the app that it's possible now. Thanks for highlighting it :)
Thanks for flagging those! I will add a "leave feedback form" in app. But I surely accept all feedback/corrections/suggestions at hello@plantspak.com and there is a contact form on the web platform as well.
And i will fix those UI issues asap :)
thanks and great question! I run automated scripts every week now and it looks back ~9 days, not 7 - a deliberate overlap buffer so nothing that changed between runs slips through, but for now it's not automatic - it produces the report for me to work on. I'm considering automating it at some point.
Valid point, as I mentioned in one of previous replies - this is my first ever mobile app and I've used some things along the way that would not work with F-droid builds right away, but I'm working on it as we speak, to make an open source version and make it available for public.
Also inside the platform -> you may delete your account at any time and I commit to never use any customers data outside of the customers experience with a platform itself.
I have a plan for a dedicated F-Droid version of the app. And hope to launch it during the summer still (hope the new google approach to apps will fail as well). It's a little more tricky for me personally as this is my first-ever production-grade mobile app, so it takes some time to figure out the details. For example, push notifications will not work, for better or worse and I'd like people to get notifications when there is a new vegan spot in their city + I use Expo (this felt like the best path initially) which will not work well for F-droid builds.
So it will take some time - but I will open source it and move to F-Droid and hopefully other catalogs as well.
There are more details on web version, probably still not enough. I did not want to make the place page to crowded with more "technical" data. But I will reconsider it moving on. You may also help me verify the places by markign them in app or on web or suggesting exact changes on web :) thanks
wow, happy to hear that! I'd still recommend to check at least google maps to be sure it's open and opening hours are correct. My data is OK, but I can't guarantee yet, unless the verification badge clearly states that it's verified (I've checked quite some places manualy).
I keep improving data every day. So thanks for an encouraging comment :)
I've build a platform initially based on OSM imports. It's good to have it, but the data quality is not reliable enough. I keep researching and cleaning up the data + working on repeatable import from OSM + OSM enrichment, but it's quite tricky on a scale. Mapped ~50k vegan and vegan-friendly places so far and everyone can add/save their favourite places, add reviews etc. All free, no ads and run by 2 people. And mobile app is available - maybe this will be another optional alternative to consider :)
Contributing back is something I'd genuinely like to do - the challenge is that bulk OSM imports require a formal community proposal, import account, and changeset review process, so it's not as simple as a one-way sync - will work on that once will be more confident on the data quality. That said, individual fixes you add to OSM will flow into PlantsPack on the next sync.
For the fields that matter most:
- diet:vegan=only - this is the single most useful tag; puts a place in our 100% Vegan tier
- diet:vegan=yes - vegan-friendly
- diet:vegetarian=only or diet:vegan=yes together - also vegan-friendly
- Standard name, addr:*, amenity, cuisine for the base record
If you're updating OSM entries for vegan restaurants, diet:vegan=only is the highest-impact change you can make - that one tag is enough for PlantsPack to promote a place to the fully-vegan tier on next sync. We have 10+ steps verifications and enrichment process for each place, so even if places is not fully described on OMS - it may end up being better represented on our platform + we run extra checks to verify its vegan_level and status with Google API and AI checks.
Indeed, that's part of the mission! I'm still educating myself in terms of veganism (being vegan for 2 years so far) while building this, so it takes some time to make it good, but I'm genuinely impressed with how far I could get so far and I have no intentions to slow down and your comment is very encouraging to keep pushing it forward :)