We definitely hear you but the package description was really meant for dashboard use, not SDK use. It’s still definitely on our backlog to implement but the issue is that the package description isn’t returned in our offerings API endpoint, which makes it impossible for the SDK to pull it from RevenueCat. We try to be very conservative with the updates we make to our REST API in order to maintain backwards compatibility, so a package description field would be scheduled for a larger v2.0 release of our API.
For now we recommend relying on the offering description to describe the packages as a whole (for example you could have a paywall with a heading displaying the offering description and buttons for the monthly and yearly packages.) You can make more than one offering to group similar packages together so that the description can cover all of the packages in the offering.
Otherwise you could host a simple map of packages to descriptions on a basic web server and fetch that map in your app (this is what we recommend for more advanced use cases, e.g. a catalog of consumable products.)
Let me know if you have any other questions.