Hi SparkIO Community,
This is my first post. I’m a software engineer with a masters in computer science.
This is SUCH an awesome product.
After 12 hours of experience I have a few product ideas.
The initializing of the wifi settings from IOS is a little buggy. Maybe it’s my network? I am using an Apple Airport Extreme with WPA2, but I only got it to work once. Other IOT devices publish their own SSID’s and let you connect to that SSID from your phone or tablet initially to setup the wifi settings. I ended up resorting to the Serial update because it just took ages / only worked once.
I wish there was a way to reload the Tinker Firmware without going through the wifi settings. (though I’m sure that I will also be glad that there is a way of updating the wifi settings without reloading the Tinker Firmware app) The two are mutually exclusive.
Currently when we crash our custom code, say by dividing by 0 or traipsing off the end of an array (lets not pretend here, we’re all professionals), it reloads the custom firmware and restarts automatically. THAT is cool, but I’m not sure that’s 100% what I want. I could see that being useful when I’m DONE with an application… if for some reason my “finished” application crashed, I would want it to automatically start over. What would be better during development is for it to reload the tinker firmware if it crashes. What might even be better yet is to reload the last saved and verified firmware from the cloud. Look at it from a developers stand point: I want to be able to do development remotely.
We could have a bool for load Tinker Firmware on next Restart. That alone would be a catch all for development.
If the spark has a valid wifi connection it should never need to be reset to factory default.
It could log into the cloud service and pull down a bool for what to do next, then do a default action if that times out.
We should have a Create Access Token in the cloud service settings tab.
Also, under the Cores tab, there should be a few auto generated URLS such as, List Currently Declared Functions, and List Currently Declared Variables. If there are functions we could generate buttons to call them. If there are Variables we could click on them for their current value.
The idea of the Access Token was not immediately obvious, nor were the URLS for accessing variables.
It seems like an easy couple things to do in the cloud service.
Just some thoughts from a 12 hour NOOB.
This is SUCH a cool product.