How to access NFC Secure Element in upcoming BB10 handsets and platform? - security

Since straight Java development isn't going to be supported on BB10 (Am I right?), at least not without using the Android Java Runtime (which I don't want to use), I'd like to know if there will be official support and an official API from RIM for accessing and writing on the Secure Element of the upcoming BB10 handsets. I'm a developer who's considering the BB10 platform for developing an application which will need read/write operations on the Secure Element. Would that be possible? Would I be needing special permissions and/or keys from RIM?
Apparently there's not much documentation on the subject so far.

They have removed the SE on BB10 and left only the UICC...And we feel it's a good thing, as there were loads of issues with accessing the SE of a SIM

After some posting on other forums, I learned that there is indeed an API for accessing the SE in the upcoming BB10 platform. It was included in the BlackBerry 10 Native SDK (Beta 2). So far, it seems it serves my purposes.

Your best bet would be to go to the RIM issue tracker site, you can get access if you make an account at the BlackBerry Jam Zone. Submit an issue under the BlackBerry 10 project making the business case for what you want to do. They may be able to tell you what their plans are, but there is still some mutability in the road map if you can make a strong enough case.

Related

How to develop Spotify Desktop Applications, now Libspotify is discontinued

have done my due diligence, and not found any other posts that answer this question, but as usual, if you know a similar question, point me that way!
I noticed a long time back that Libspotify has been dicontinued:
(https://developer.spotify.com/technologies/libspotify/)
So, my question is - what should we do for developing Desktop applications?
They do state: "We hope to be able to provide you with a new library for other platforms." But, this has been going on since 2015!
I have seen many projects in GitHub still using Libspotify - so what should we do? An update was promised "in the upcoming months" but I've not seen anything yet.
What should we do for developing Desktop Applications?
We at Spotify don't currently provide playback as part of our platform offering outside of our iOS and Android SDKs, and I don't have any updates on that at the moment. As mentioned on the website, we hope to be able to provide playback SDKs for more platforms in the future. We don't support any new development on libspotify.
You can use the Spotify Web API to interact with Spotify in a variety of ways, including getting information about metadata, and accessing/modifying user libraries and playlists, which may be useful. You can also use the Applescript API to control playback on macOS, which may also help.
The Spotify Web API is pretty straight forward to use. Of course it defines the protocol rather than implements it so it is OS independent.
I put together a few classes to help unwrap some of the JSON parameters simply. These were written in Swift for macOS.

How do I get a list of ssid from browser?

I need to build a web based application that can list available ssid in the area.
From my understanding, these probably can do what i want
Java applet
Adobe Flash
However, Im not sure whether these can do or not
HTML5/JavaScript
Java Web Start
I'm a .NET developer and I'm not familiar with these web technologies.
Are there any other method to get a list of SSID that i have not mentioned?
Thanks.
You'll never be able to list available SSID's with HTML5, Javascript, or any other strictly web-based technology. That's a very low-level task and won't be natively possible in any browser for security reasons. That being said, you may be able to draw on some technology like Java Applets, ActiveX, or even Silverlight 5 if I remember correctly. I don't know your project requirements, but you're better off creating a native application for this type of feature. If this application is being used by/sold to the general public, you're setting yourself up for a lot of headache by going with Applets/ActiveX/etc.

Can I use Yandex Maps in a Nokiax app?

I need to use Yandex Maps in an app instead of Here Maps. Could this be possible? Any hints or tricks to help me?
Thanks
Basically the rules of using APIs is very simple. If the API is not requiring any parts that are not available in the platform, then it works.
Thus if the API is using parts that are supported in AOSP 4.1.2 API level 16, and using any Google services, then it is likely to work just fine.
And you can always check the compatibility with free online tools very easily. First go to Online Analyser drag and drop the APK there, and let the tool check the compatibility issues.
Then you can also use a real device for testing, just visit Remote Device Access, and reserve a device for testing your app.
Both steps should onlky take you couple of minutes to complete.
For Yandex maps, you would need to visit their developer site to see how the maps API can be used, and what restrictions they would pose on utilizing the API.

Are there any embeddable browsers available for WinRT?

The html + css standards difficulties of supporting IE as a browser translate into using it as part of the WebView control where there are further limitations on functionality.
Other difficulties include:
It renders on top of the XAML
- Using the recommended approach of WebViewBrush isn't a valid scenario if your pages have dynamic content on them.
It doesn't support HTML5
You can't access the content
You can't access the content
- Trying to debug issues with it is nigh on impossible.
Are there any alternative embeddable browsers available or in the works?
To answer your question, I think Jim is correct that there are no other embeddable browsers available, and it's not something I'd expect to see.
I would also recommend that you review the Windows Store Certification requirements, as many may be applicable in this case, including:
2.4 "The primary experiences your app provides must take place within the app" (as opposed to coming from the web)
3.6 "Your app must fully support touch input, and fully support keyboard and mouse input" which covers requirements for touch, including the need for your app's touch support to be consistent with the Windows 8 touch language.
While it's obviously appealing to re-use content across platforms, it's also important to keep in mind that this may lead to degraded experiences for end-users. If those experiences are too far afield of the established behaviors for Windows Store apps, they could also result in your app failing store certification.
For more info on Windows Store app development, register for Generation App.

NoSQL databases that officially support MonoTouch

I am having trouble finding a NoSQL databases that officially support MonoTouch via a local DB on the device. If their are, could someone provide a list of them here.
According to http://nosql-database.org/ there's siaqodb. Note that others might support MonoTouch without being mentioned in that site.
Edit: a few more clicks shows that HSS Database (from the same list) also supports MonoTouch.
You might also want to look at which ones support iOS (e.g. with Objective C) and see if bindings are available (or write your own).
Take a look on Couchbase Lite xamarin's component
RavenDB supports an embedded mode, and can run on Mono using the "Munin" storage engine option.
Although, there has been talk in the user group lately about dropping Munin, and it's not usually recommended for production, so it may not be a viable option.
I've not heard of someone using it with MonoTouch specifically, but there are some running it on Mono. If you try it, please update comments here with your findings. Thanks.
A bit late, but still relevant:
I'm the author of MarcelloDB, and I just released version 0.3.0 on nuget.
MarcelloDB is a document DB, built specifically for mobile apps (light-weight, low memory usage) and supports Xamarin Android and iOS as well as the windows platform.
I still have some features I want to add before reaching v1, but the file format and existing api are allready quite stable.

Resources