After I managed to force my Galaxy Watch to show the RSA confirmation screen ready for debugging, I reinstalled Tizen Studio 3.7 with Samsung Certificate Extension (terribly important, I don’t really understand why it is not installed by default; without the Samsung Certificate Extension Tizen Studio installation is totally meaningless) for deploying on real device and making a web demo and debugging was really straightforward.
Tizen News Feed Demo Running on My New Galaxy Watch (Tizen Studio 3.7 is out)
Now I am ready for prime time, and super happy, I worked really hard.
Thank you for the great Tizen community and support.
Hi Miklos,
Distributor Certificate tells a specific device who is installing the app and it is safe to accept that app. If you want to install your app on a different device you would need to create a new distributor certificate for that device. (or via the beta testing option on the Galaxy Store) This prevents a hacker from putting a virus in a .tpk file and pushing it out to the public.
Samsung replaces the developer’s distributor certificate with theirs which is recognized by all devices.
Ron
Samsung Developer Program
Thank you, Ron!
Let me ask you an important concept. Are you at Samsung/Tizen planning to support Progressive Web Applications (PWA) with HTTPS-mandatory-sources, Service Workers, Manifest, Web/Browser Storage API and Indexed DB? PWAs are supported neither on Android Watch nor on Apple Watch as far as I know. This is where Tizen could be progressive. I love the safe nature of signed, self-contained Tizen web applications, but PWAs are the main stream today for deployable, off-line operable web apps. What do you think?
Thank you so much for the support, Miklos
HI Miklos,
I have no idea. You’d have to look at tizen.org that is way out of my scope of knowledge.
Ron
Samsung Developer Program
The reason I am asking was that apart from Google, both Microsoft, Samsung (check out this page on Samsung) are promoters of PWA, and recently Apple supports PWAs, too.