94 karma · joined September 21, 2010
http://www.stencyl.com
http://www.linkedin.com/in/jonathanchung
I concede though that if you go with out of the box LNF's, even Nimbus, your results will not be up to par.
The same friend, just for kicks, submitted a deliberately broken app that didn't crash but showed a blank screen after launch. It also got approved without incident. It's like Apple just ran automated tests, but no human ever saw it.
I have a feeling that Apple's process varies depending on the kind of app (free vs. paid), the platforms you're targeting and your past history.
These aren't exactly no-name companies or recruiting firms but the actual companies themselves - we're talking about Zynga, Playdom, ngmoco, etc.
Is this something other founders have found?
I prefer to take my yogurt plain and mix in my own jams, rather than the fruit on the bottom variants. That gives me more variety than the default flavors provided and lets me control the amount that goes in.
Our closest competitors locked themselves to one platform and have faced challenges trying to go cross platform.
With Whole Foods, the best (and most pragmatic) deals they offer aren't at all on their website and must be tracked in store. I think that there is a market for including Whole Foods, not in the novelty items, but in comparing natural/organic commodities that are popular enough to be carried by Target, Safeway and even Costco. On those fronts, WF is frequently the cheapest.
Do you have plans to, perhaps, crowdsource some of the price reporting similar to how gas price comparison sites are done?
For example, Whole Foods and TJ's are substantial players in the Bay Area market as well as discount stores like Target where there's a mix of the everyday low price model and sales on loss leaders. What are your plans to tackle stores like those?
Overall, this is a good start, and I look forward to seeing this fleshed out more.
I think that the term "poverty" relates specifically to developed countries where fast food is the cheapest way for the poor to feed themselves off the dollar menu.
If you're looking for a GUI as opposed to a programming API, in addition to the fine options above, my startup (http://www.stencyl.com) also does this and is based on Sparrow (and Flash for exporting to the web).
However, I'll be realistic and say that if you're making an RPG, you'll find it much easier to build it by hand.
I'd love to see a posting about the evolution of the mascot and overall design of the app. It's pretty slick.
- Not able to think logically. There's only so much you can accomplish if you take logical thinking out of the equation, and when you do, the creations are underwhelming. Many startups set out to make creation easy, and that works to some extent, but the real solution to the problem may be to try to educate users and bring them up to a minimum bar (learn how to fish), rather than trying to lower the bar to the floor (give them the fish). This would be suicide for most startups, but the users of creative apps are more patient and more willing to learn and grow with the app. Sure, we'll shut out some people this way, but we want to lift up the right, motivated people, rather than trying to lift the entire world up.
- Can't draw/other artistic skill. Shockingly, this ends up being a big problem, and people absolutely hate using placeholder art if they can't draw. We've addressed this by integrating a marketplace for pulling in all kinds of resources.
- Can't work with other people. Many game projects fail due to bad communication (if you're not working solo). They start out strong when brainstorming and then die somewhere in the middle, usually when the members fall out of regular contact or don't know what's going on. We've integrated some features into our app to directly address this after observing how our users interacted with each other on several group projects.
- Set their sights too high. No, you're not going to create an MMORPG or RTS as your first project. ;) This one isn't directly addressed by our app right now and falls more under the umbrella of general user education and progression. One idea we have is to incorporate game elements (turning game creation into a game?) to nudge the user towards making baby steps towards completing something through a quest structure, rather than trying to let them go free from day 1.
The take home point is that like any startup, what you set out to do ends up evolving as you move along and that the problem you're solving turns out to be different and sometimes larger than what you originally expected.
What we have is working, and it's working well, but as we press forward, we find that our strongest value proposition is no longer the code-free aspect, which turns out to be just one small part of a larger puzzle. Once you remove that roadblock, other pain points come to light that are far more difficult to solve.
Our ability to deploy to Windows and Mac is giving us a leg over some competition that's unable to serve the larger Windows market. Being able to knock out new features very rapidly (within minutes/hours) is another advantage.
Reminds me of PG's essay about how Viaweb was able to implement a competitor's feature the same day it came out...
Investors like to see traction in your product, and if you lack it, they'll continually label you as "early."
Avoid cold calls unless you have no other way in. Get introductions through your network.
See: http://www.nicholas.duke.edu/thegreengrok/farmedfish-pnas092...
Recently, I've seen more of a shift to grains, but that reduces the nutritional value of the fish.
Slaughterhouses and meat processors in the US, in particular, are notoriously opaque about their operations in a way that would make Apple's practices seem lenient by comparison.
I hope that they ensure a smooth transition of the responsibility to Oracle and perhaps even hand over some of the existing work, if licensing permits it.
"I want it to be as beautiful as possible, even if it's inside the box. A great carpenter isn't going to use lousy wood for the back of a cabinet, even though nobody's going to see it."
I can't speak for that today, but my source for this info was the Java Swing team themselves since they talked all the time with the Java "team" at Apple.
While I concede that Java has lost relevance on Mac, there are outliers like ourselves who've written native looking Java software and don't have a viable route should the worst case scenario arise.
My only inside knowledge is that the Java "team" within Apple was very small, which explains why it constantly lagged behind on updates.