You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I apologize for any inconvenience this may cause; this is not precisely an issue report. I am currently developing a library designed to simplify the implementation of ads in Jetpack Compose applications, called JetAds.
I would greatly appreciate your feedback on this library, particularly regarding its functionality and usability. The philosophy behind JetAds is "plug and earn," emphasizing ease of use. While I believe the core functionality is robust, there are certainly areas for improvement in how the library can be consumed.
Your insights would be invaluable in helping me enhance the library further.
The text was updated successfully, but these errors were encountered:
The BannerAd is loaded by the composable. This means that preloading and pooling solutions which require a separation of the adview and the composable are not possible. Also, Banner variations (Fixed / Adaptive) required their own composable and can not reuse a single banner composable. There is some layer friction here.
The Callbacks do not return a BannerAd when loaded, this means that publishers will not be able get a reference to the Ad for things such as ResponseInfo.
Thank you very much for the feedback, I will work on these corrections. Can I keep in touch here if I have any questions during the development of the library?
I apologize for any inconvenience this may cause; this is not precisely an issue report. I am currently developing a library designed to simplify the implementation of ads in Jetpack Compose applications, called JetAds.
I would greatly appreciate your feedback on this library, particularly regarding its functionality and usability. The philosophy behind JetAds is "plug and earn," emphasizing ease of use. While I believe the core functionality is robust, there are certainly areas for improvement in how the library can be consumed.
Your insights would be invaluable in helping me enhance the library further.
The text was updated successfully, but these errors were encountered: