The problem is that with codenameone you cannot experiment with ad networks. You are kind of locked in to using only ad networks that codenameone supports.
Let's agree on that it's _much_ harder to experiment with different ad networks than it'd be with native coding. E.g. even Shai and Chen tried hard to make MoPub/AdMob work and failed so far..
On Wednesday, September 25, 2013 5:45:30 PM UTC+2, shannah wrote:The problem is that with codenameone you cannot experiment with ad networks. You are kind of locked in to using only ad networks that codenameone supports.I just want to comment on this one point because it is wrong and defeatist. You are a software developer. Codename One provides you mechanisms to implement HTML5 components, native components, or pure Java components on top of the CN1 stack. You are *not* locked in. If you run into missing functionality, you have the ability to just implement it yourself. You don't need to rely on the (very busy) CN1 development team to implement everything for you.Steve
--To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/6218596c-b67d-43ed-bbef-970b38a307b1%40googlegroups.com.
You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codenameone-discu...@googlegroups.com.
Visit this group at http://groups.google.com/group/codenameone-discussions.
Let's agree on that it's _much_ harder to experiment with different ad networks than it'd be with native coding. E.g. even Shai and Chen tried hard to make MoPub/AdMob work and failed so far..I don't think it is _much_ harder. Just take it one platform at a time. If you were to go with your suggested "easier" alternative of creating separate native apps for each platform, you'd have to implement one platform at a time anyways. I took a quick peek at the Vserve android docs and it looks pretty straight forward for implementing in CN1. Keep in mind that it is _much_ easier for you to implement an API for your own purposes than it is for Shai and Chen to try to adapt it for everyone's purposes because they have many more considerations to make. I.e. you can use a quick and dirty approach to get the job done. They can't.Therefore, just because Shai said that something was difficult to implement CN1-wide, doesn't mean that it will be difficult to implement with a more narrow scope (such as your project).-Steve
On Wednesday, September 25, 2013 5:45:30 PM UTC+2, shannah wrote:The problem is that with codenameone you cannot experiment with ad networks. You are kind of locked in to using only ad networks that codenameone supports.I just want to comment on this one point because it is wrong and defeatist. You are a software developer. Codename One provides you mechanisms to implement HTML5 components, native components, or pure Java components on top of the CN1 stack. You are *not* locked in. If you run into missing functionality, you have the ability to just implement it yourself. You don't need to rely on the (very busy) CN1 development team to implement everything for you.Steve
--
You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codenameone-discussions+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/6218596c-b67d-43ed-bbef-970b38a307b1%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to codenameone-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/611f2b82-5531-42ec-b6d1-8eded0a2eea2%40googlegroups.com.