I've used Parse extensively as a backed for iOS apps before and lately started trying out Firebase as a replacement. Firebase seems like a decent alternative so far, but there's 2 important features that I'd like to see:
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.
First of all, I realize this game is very similar to some existing games out there - I drew inspiration from puzzle games such as Candy Crush
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!)
Yea, the current version uses a webview to show the street view, and moving/shifting the street view tended to make the app crash, so that's why it's disabled.
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.
Yup, it was adapted from geoguessr.com, and I'm trying to extend the concept by adding different game modes and in-game hints
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!
I'm confused why they decided to immediately remove Summly from the App Store rather than use it to drive traffic to other Yahoo apps - anybody know why they did this?
Cool technical presentation, but trying to optimize moving average trading strategies is a fool's game - you might find a set of parameters that work in all out-sample/cross-validation tests, but there's still a good chance it'll lose money in actual trading going forward - market paradigms can shift, unforeseen world events, t-cost/slippage higher than what the model accounted for (especially with more frequent rebalancing), etc.
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
This uses Backbone.js on the frontend, and each time you change sites on the left sidebar, a "pushState" event is triggered, which saves the current state of the page (and the back button will cycle through those saved states)
Seemed like this would eventually happen since Google stopped updating Reader (and its APIs) a few years ago
I've also been working on a similar news reader app called BlogRoll: http://blogrollapp.com
It can import your Google Reader feeds and has a tiled layout (which may not be everybody's cup of tea), but it works well for photo-focused sites like food and fashion blogs, and it handles other news sites and blogs quite well too.
Many large asset managers have mandates to sell their losers and cut losses, or may be window dressing before the end of the quarter and don't want to show to clients that they hold any FB stock on their book.
From the article: "That means that Facebook's enterprise value is greater than 10x current revenue run rate and greater than 25x EBITDA. These are big multiples folks. I am happy to take those numbers for any company out there."
The bigger those multiples are, the more "overpriced" a company is, so it should actually be less attractive of an investment.
This isn't a big deal at all - it's basically just a market order. Whoever put in that order will just get filled at the best ask price - probably around $41.
You can wait for the timer to count down or click the arrow to the right of the timer to skip to the next day, then it will show your profits or losses for that day.
The goal is to increase your money and experience over time, which will let you level up and unlock more stocks, allowing you to expand and diversify your portfolio.
Let me know if you have any other suggestions, thanks!
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.