01-27-2011 06:51 PM - edited 01-27-2011 06:52 PM
Just thought I post an open question here as I'm curious about everyone's thoughts.
As I've been learning all of this from scratch my intention from the start was to submit my app in a very basic state - without all my content, without anything fancy in it but done enough to work the way it is supposed to. Once submitted though, I would continue to work on giving the app a "facelift" - making it not only look pretty but perform in a way that would be very enjoyable to users. I would also add a significant amount of content.
Now, my thought behind this was that by submitting it early would at least get me in the door, and future upgrades and updates would be a smoother process. I would be hopefully have these done before the PlayBook is launched so the end user would never even really see this basic state, but it would allow me to work without worrying about a deadline or stressing about approval, thus allowing me to learn without feeling frantic.
Just curious if anyone else has taken this approach, or if everyone else is submitting their app once they feel they are "done". (and I realise most apps are never done and updates are an ongoing procedure).
01-27-2011 06:59 PM
the only thing that comes to mind on this subject is that dreaded line from the terms and condition that states if they feel your app has a high chance of selling and / or being downloaded by the consumer it'll be approved. so its in their discretion wheather or not your app will be something people will use. so if it has enough features to meet that requirement it'll be fine in my opinon. so you just have to ask yourself, would you download and use your app? just my two cents
01-27-2011 07:04 PM
No offense to any of the other developers out there, but I've seen some apps that literally look like they took no thought, UI or UX considerations into account... Yet they were approved...
However, you can say they were in a fully "complete" state, as in no new features (that we know of or can assume).
In my case, I want to release the app, but know that all the stuff I want to pull off could take a month or more of development, and would put me way passed the offer deadline.
In a way, I want to be in the mind of an approver to gauge what probability of success I'll have getting approved.
01-27-2011 07:21 PM
I'm with you killerspaz, all of my content needs a once over to get formatted for the PlayBook and that could take me weeks (while juggling learning new code and that little thing that takes 8 hours of my day called work). Also learning how to implement new features isn't exactly a walk in the park.
I'm aware of the line you mention JRab, and while yes, I would download my app in the state I plan on submitting it in, as a user I would feel disappointed in a lack of features and content. However, I've had to start making a list of all the updates I want to include as I learn more and more about what I can do. And these wouldn't have to come all at once. So like I said, by the time users even see the app on their device they would probably have 90% of the content I'm planning on adding. I guess it just comes down to taking the risk of hoping for approval with maybe 25% of planned content.
(And as for the comment about apps being approved that don't come close to following the UI or UX guidelines, I have to say that many of the apps shown off by BlackBerry don't even follow these guidelines strictly so I'm a little torn on what their stance even is).
01-28-2011 02:44 AM
01-28-2011 10:57 AM
01-28-2011 05:32 PM