So... 2/5 passed certification in the end.

Hiya,

I want to preface this with the following: this is not a complaint and I am well aware that the negative results below are my responsibility. I misjudged Samsung's Certification process and that lies on me. The below is just my own experience and results that I thought I'd share.

I submitted five entries to the challenge (all of which are in my portfolio). They were all submitted at the end as I was still learning the platform and submitting one earlier didn't seem useful as I was constantly refining my overall codebase. This is especially true as none of my code is truly native: I modified a cross-platform library known as "libgdx" to support the device so that I could more easily port these application to other platforms if I wished. I do plan to, at some point, write up a guide on how to use libgdx on Tizen Wearable.

Anyway... My most complex entry with the most work put into it was rejected sometime between 1.5 and 3 hours ago (the entry being "Puppy Pedometer"). I've submitted the update already to the minor problem (my screen override setting, that I could have just omitted from the user entirely in the first place, had a bug) but there isn't much of a chance of it making it through in time.

While my fault above, two entries that I lacked giving any real customization options on, "Alien Invasion" and "Penguin Survivor", both made it onto the store. It seems simplicity was a key to making it through Certification. "Penguin Survivor" took only 6 days to make it for sale while "Alien Invasion" took 8 days.

My last two were clock based applications. "AnalogWatch", "ClockWidget", "StopWatch", "VoiceRecorder", and "Pedometer" from the Tizen Wearable SDK Examples (5/9 of the examples with the other four not requiring a time or date) all use "new Date()". This, as another thread showed, is not the API one should use when getting Time information as a bug exists when dealing with timezones. So... one of my clock applications was rejected for following the preferred API shown in their samples and Samsung Certification would reject their own sample applications if using the same test case they used on me. The other one I self-rejected since it would have the same bug and was still in the "Under Device Test" phase. Technically, both of these have a shot of making it still having been re-submitted last Wed, but I rate the odds at very low with how quickly things are moving through Samsung's Certification at the moment.

As mentioned initially, I'm not demanding that deadlines be extended or saying I'm not to blame for not being more cautious with certification. I respect ChallengePost and Samsung's right to run the contest as they see fit and appreciate the opportunity to have competed. :) Plus I still had two of my entries make it through which is certainly better than zero (though I really wish one of those two had been "Puppy Pedometer"). Just my own experience for this phase of the contest that can be considered. I look forward to improving upon whatever does make it by the deadline and learned a bunch about smartwatch development regardless. Thanks!