smnl
Joined 15 years ago
Joined 15 years ago
Secondly, this game was developed from start to finish in just 2 months' time, owing to Sprite Kit's simplicity and elegance. Though there's not much example code out there for Sprite Kit given how new the framework is, it only took a short time to start drawing some graphics and animations. However, for more advanced things, such as sync'ing and sequencing several groups of actions/animations/sounds on multiple on-screen sprites, that required more custom work on my end (which could be worthwhile to explain in a blog post later on).
Anyway, try it out and let me know what you think. And if there are any other developers out there using Sprite Kit as well, I'd love to chat or get in touch! (especially if anybody has experience porting a Sprite Kit app to Android!)
However, now that Google's added street view to their official iOS maps API, I'm planning to integrate that and it may allow features such as moving and zooming.
In reply to your questions: 1. What do you mean by similarity measure? Currently, the scoring is just done on a tiered basis on geographic distance, though that scale might be worth adjusting
2. Currently, it uses a webview to show the street view, and moving around is disabled because that tended to crash the app. However, now that Google just added street view to its iOS maps api, I'm planning to integrate that
3. Yes, all of those things you listed can help determine where a landscape is. I haven't thought about formally classifying those features, though it could be something worth exploring
Thanks for the feedback! Will reach out to you if I figure out a way you can help with this!
If you actually want to trade moving average strategies, your best best is just to diversify and run several different strategies across a variety of parameter sets and across various sectors/asset classes, without trying to overly optimize a single strategy
Would this still be able to capture those events? And if so, how?
1. Always immediate updates for Remote Config flags - currently Firebase uses old cached flags for up to 12 hours and only allows immediate updates in the "developer mode", but in production, sometimes you need to change a config flag for all users immediately, perhaps to fix a bug, and can't afford having clients still use the old cached values.
Also, it would be nice if Remote Config supported additional data types like arrays, dicts, and dates.
2. A non-realtime key-value datastore - most apps don't require a realtime database, so it'd be great to have a simple datastore where you don't have to worry about managing the number of simultaneous connections.