Shouldnât this be rolled-up under âBugsâ and not under âHow Toâ? Not sure how Glide tracks/follows/handles these. It seems that a lot of heavy lifting is done by âThe Communityâ
These both seem like they could be related and I am tracking this since I am demoing an app with 2,500 rows with ROW-IDs stored in a google sheet and this is disconcerting.
But I am confused on how Glide supports end-users especially around BUGS.
Weâve been chatting in private, letâs exchange in public so others can also benefit.
It is true that a lot of issues are solved in the community forum. Glide has grown quickly and a lot over the past two years, the enthusiasm and expertise of the community is one of its superpowers: it probably fosters member growth, buzz, etc. And the community is happy to contribute, or it wouldnât be doing it.
Collectively, the members of the community have accumulated a huuuuge amount of knowledge and expertise in Glide. So when do you turn to the community, and when do you turn to Glide support?
For questions related to the product directly, how toâs, best practices, display, data structures, actions, project settings, ⌠I would always turn to the forum first. For issues that are under the hood, where someone would need to look into my app, for major crashes or bugs, or for billing and account issues, then only would I turn to support. Keep in mind that at times, what might appear as a bug is actually unexpected behavior due to some lack of understanding of the platform. Of course this might be an indication that Glide still has work to do to simplify our experience as developers, but it also means that someone in the community might be able to solve your issue which wasnât really a bug in the first place.
At the end of the day, wherever you ask, youâll be welcomed by people happy to try to help.