I am trying to integrate card.io sdk in my android app. I was wondering if it supports non-embossed cards as well as it is very important for the kind of app I am working on.
I went through some old posts where it was mentioned that it is not supported yet. I just wanted to know if -
With latest release 5.2.0, is there any support for printed cards?
Is there any plan for near future, to support non-embossed cards?
Thanks
Unfortunately, printed/non-embossed cards are not supported as of card.io Android SDK 5.2 (nor in card.io iOS SDK 5.3).
The feature requires a non-trivial amount of work, but if you're interested in adding the feature, you may be able to look into the source repositories and try to get a few people on GitHub to help contribute. (Android, common dmz).
Related
Is there any information, updates, or documentation regarding Codename One's WebRTC support? There was a mention of it months ago in this comment on Stack Overflow (AntMedia Native Interface issues), but then I haven't heard anything more about it.
For the time being, I'm supporting live streaming on AntMedia via native interfaces that do live streaming with RMTP, as on my own I couldn't find a way to support WebRTC in Codename One. Unfortunately I realized just today that the RMTP support on Android doesn't work anymore (I don't know why, in the past months it worked)... anyway I've always considered RMTP as a temporary workaround, maybe this trouble is a good opportunity to switch to WebRTC.
I've seen that Steve has quietly created this cn1lib, which has not been announced (maybe because the work is not yet finished?) nor is it present among the extensions that can be installed via Codename One's Control Center:
https://github.com/shannah/CN1WebRTC
I found the documentation here:
https://shannah.github.io/CN1WebRTC/javadoc/
but comparing this javadoc with the documentation provided by AntMedia I just don't understand what I have to do, as AntMedia provides its own SDKs for Android and iOS, provides documentation to use them, but I don't understand how I can use in their place the cn1lib made by Steve. Obviously porting their SDKs is not easy, otherwise I would have already done it as the first option. In any case, the AntMedia server should be independent from the SDKs used, as it should use standard protocols, if I understand correctly.
Specifically, I have a server running AntMedia Enterprise Edition 2.1.0, whose documentation on WebRTC support is here:
https://github.com/ant-media/Ant-Media-Server/wiki
Thank you
I haven't used AntMedia Server, so my following comment is based on 10 minutes looking through their documentation.
It looks like they provide their own API that is distinct from the standard WebRTC APIs. The Codename One WebRTC lib is built on the standard WebRTC APIs. I think that the best route, if you want to use AntMediaServer's APIs is to create native interface wrappers for it.
It is also possible and likely that you can just use the Ant Media Server and then use the standard WebRTC API to connect to it. If this is the case, then you would be able to use the cn1lib with it. However, their documentation only seems to show how to use their custom API for the client.
I need to know if there is an alternative to crosswalk that i can use in my ionic project. On Android OS 4.1 my app does not act normal but it is okay with higher OS's, i added the crosswalk plugin and it works very well across all OS's but then i am faced with the challenge of larger apk size which i do not want as my boss want's the apk as small as possible...with crosswalk what used to be less than 8mb becomes 36mb which i feel the increase is sooo much...please has anyone come across a similar situation and found an alternative to crosswalk or maybe someway to make their application work properly on lower OS?
There is no crosswalk alternative at the moment. Crosswalk has also been discontinued as of February 2017.
For anyone building Cordova apps in 2018, the best way forward is to take advantage of Progressive Web App capabilities.
My company recently came up with an idea to include using smartwatches with the app I wrote using codename one.
Is this possible? If yes, which libraries do I need?
We are evaluating the possibility of smartwatch support, this depends on customer demand.
We currently have a major enterprise prospect that has expressed interest in this but hasn't signed up. If your company is serious about this please contact us directly.
Assuming we don't go that route or you need something immediately this depends on your supported platform, you would need to use native interfaces for most functionality. In Android notifications (which we support) should work for Android wear. In iOS we are transitioning to the new xcode 7.x which should support smartwatches too but I'm not sure what would need doing.
I finished 1 Project in Pure GWT and 1. in SmartGwt. However I want to support a Mobile version of both Projects now.
I found :
mgwt -> which has a medium Community, documentation is well made and under heavy development.
SmartGwt - Mobile -> which has a low Community, documentation is not that good, development idk..
Both have a Showcase site.
I personally liked the SmartGWT-Mobile Showcase better.
But the point that mgwt gives me better support is huge!
My questions is now :
1.Mgwt or SmartGwt mobile or together?
I think the answer depends on your strengths itself. I tried both of them when I started building cross platform app.
Smart GWT Mobile
+ve:
Easy to start working with
Large number of ready to use components.
-ve :
Support is an issue.
And if there is some thing the framework didn't support, it was hard to get it done.
The Smart GWT performed best when the server side also used Smart GWT. Even though Smart GWT mobile is free, I was not comfortable since they may tie it up to server similar to Smart GWT some time in future.
mgwt
+ve:
of course, open source.
good support on google forums. Normally the questions are answered on mgwt forums and occasionally Daniel Kurka also jumps. Daniel is creator of mgwt and he is also a member of GWT steering committee.
The themes in mgwt are good. The L & F just matched the ios or android platform.
I can extend it easily if some component is not available or if I didnt like any thing.
-ve:
limited number of components.
It takes time to set up and start using.
Slow updates.
Finally I went with mgwt since I have a team which can open up the code and fix it, if they see any issues.
I'm currently investigating the alternatives for crossplatform development for Android and iPhone (Windows 8 could be a nice addition). The app is basically a "map with an asociated app", and certainly not a game.
Searching here I see many outdated advice and tools from 2010/2011, but since then Apple has changed their policies and surely new things have appeared.
My current list and light research (might have facts wrong) is:
Monotouch/Monodroid: .NET (Mono) framework. Create "native" apps on both platforms. Requires rebuilding UI code (or similar things).
Appcelerator: Javascript framework to compile native apps.
Corona: Similar to Appcelerator.
Phonegap: Similar idea, but looks like it uses a wrapper to appify HTML5 content
SenchaTouch: Another HTML5 based platform.
Wink: Yet another HTML5 toolkit.
XVLM: Android to ObjC compiler, probably creating ugly iOS apps.
Unity3D: For games only.
Moai: For games only.
So, there are three main ideas, with some frameworks implementing each, it seems to me:
Have an abstraction layer over native iOS/Android code and build for each platform using the provided layer. (Monotouch, Unity3D)
Use HTML5 (coding in Javascript) and some kind of wrapper to "appify" the web content. (PhoneGap,Sencha,Wink)
Code using a framework that will output as a compilation pass (or similar) a native app for each supported platform (Moai, XVLM,Appcelerator,Corona)
The questions:
Is there a fourth idea I haven't yet found?
Is there any blatant mistake in my research for any of the specified frameworks?
Is there any known problem for map integration with any of these ideas or specific frameworks?
Only a partial answer:
Ad 2. Appcelerator / Titanium is more than just HTML5. I read this pretty extensive comparison between PhoneGap and Titanium the other day on Hackers News. I found it very informative. The link points to the HN comments, the link to the actual article is at the top.
My main experience is with Mono for Android and MonoTouch, so I can't personally speak much to the other options. I personally find it to be the best option there is, as it allows you to share a large amount of your code across the platforms (even extending to non-mobile platforms if you stick with .NET), while still allowing for a 100% native UI, which is extremely important. If you're looking for resources on getting started, I have this video which discusses approaches and libraries for sharing a lot of code across platforms, and also this book which covers the same thing, but also expands to talk about how to do things like store data, use maps, access the network, etc.
I also want to mention MonoGame, which is absent from your list. MonoGame is an open source XNA implementation that sits on top of Mono to allow you to target iOS/Android/Max OS X.
From what I have experienced, if you want to have a native app go Mono, if you don't need native go PhoneGap. Native is best of the UI is very important, ie games or fairly graphical apps. But from business type app, CRUD, Phone gap works well.