Re: 2 itunesconnect questions
Re: 2 itunesconnect questions
- Subject: Re: 2 itunesconnect questions
- From: April <email@hidden>
- Date: Tue, 15 Nov 2011 13:21:45 -0700
On Nov 14, 2011, at 5:32 PM, Conrad Shultz wrote:
> On 11/11/11 9:50 PM, April wrote:
>> Actually I had a long existing project that I start working on in 4.1
>> before the release and then 4.2 when I started icloud support up
>> until now. I've hit multiple delays and setbacks due to adding
>> features out of fear of 1 star ratings due to "It's useless cause I
>> cant..." Even though many of the features are simply moronic on a
>> touch platform. For instance the ability to draw freehand on an
>> iphone in an app for serious use.
>
> As a user, I hope that if a developer considers a feature "moronic" then
> they wouldn't include it. You of course can never satisfy everyone, so,
> IMHO, best not clutter an application with ill-advised features.
I'm working from past experience. I once released an app on mac that had nothing what-so-ever to do with movie editing (mpg,avi,quicktime etc) and because people could not use the app to string bunches of clips together I got flamed. Tons of support email, bad reviews and more than a few I WANT MY MONEY! Never mind the fact that after the first complaint I changed all the listing information and my own site so the first line of the description specifically said it could not string movie clips together.
Thus within a few weeks, I released an update with the completely moronic feature (in this app) of being able to string clips together. Anyway.... people loved it. I have never used the feature for anything outside of testing.
I think moronic is too strong of a word perhaps. But this is a touch platform, and it really has significant limits to pixel perfect editing. There are things it does that, I personally find I dunno... too ambitious for a touch platform. At least, in the case of a girl with medium length fingernails(me). Not sure if guys, and gals that trim their nails, will find these things easier than I do. Those that use a stylus will probably really like all the features. I know my stylus changes the playing field significantly. Still the freehand... Honestly even with a stylus, it's only there because I just know if I pull it i'll get slammed with "It's useless because I can't draw!" And those are always the words "It's useless because..." I'd rather risk loosing a star on an otherwise good review for having the feature than only get 1 star for not having it. :\ I know... I'm weighing asterisks at this point...
All that said though. If you have twenty minutes - half an hour (maybe a little more on iphone), you can create some absolutely stunning documents with the tools provided. Seriously. I was shocked at the results I was getting because I have such poor graphic design skills.
>
>> Anyway.... all I did when I started working in xcode 4.2 was set the
>> base sdk to 5.0. I never changed the deployment target away from
>> actually, 3.2. Later I implemented ARC but only changed the
>> deployment target to 4.2. And this project was originally poorly
>> implemented in that there were 2 separate projects, 1 for iPad, 1 for
>> iPhone/iPod. So I brought all of the code under one roof and used a
>> simple ISIPAD definition (a macro for the interfaceidiom check) to
>> figure out what should do what. not that that matters. Anyway. In
>
> OK, this is what I was getting at in my previous message.
>
> Let me make sure that I understand correctly. You started out with a
> *single UI idiom* (i.e. iPad or iPhone, but not both) project, then
> manually created a *universal* app (i.e. one for both iPhone and iPad)
> by merging code together? That is to say you NEITHER started a new
> Xcode project of the "universal" type NOR ran the "upgrade to iPad" tool
> in Xcode?
>
> If this interpretation is correct, then my previous point remains: you
> may have skipped over some important project settings that the build
> system is expecting to be configured but aren't (or are configured
> improperly).
You have it right. And you were right I misconfigured the build settings when I moved to XCode 4.2. (More accurately, did not do anything to them at all.)
I know... It would have been much better to convert, or make a new project. I didn't. fortunately the challenges did not effect the performance of the app only getting it to actually be an app.
>
>> xcode 4.1 the arch had been armv6/armv7 and I never really bothered
>> to look at it again after installing the final xcode 4.2. I built and
>> ran.. according to the bundle version script's last incrementation at
>> release 2673 times over a 5 month period. Installed at least a dozen
>> or more adhoc builds via itunes to check some built for release
>> things. never got an actual error... though I was ignoring warnings
>> in the build window. Won't do that again. so last night I was
>> surprised. Like I said stack overflow had an answer, but since
>> starting this thread I now understand the problem, thanks both to you
>> and others. Had I changed the build target to 4.3 I'd have never seen
>> the error. But because I was trying to maintain some degree of
>> backward compatibility I got the error. I did manage to get it
>> submitted with armv6/armv7 compatibility. version 3.1 may not support
>> armv6. I'm still contemplating that. mostly I hate the "What about
>> us" support emails. The ones I got a few hundred of when I updated a
>> mac app to intel only, app store only.
>
> So what did you end up doing to get it working? I thought you were
> using a compiled library that was armv7 only?
I changed the deployment target to 4.3 -all is fine but i've cut out the armv6 support
>
>> So I guess, technically if you can consider it converting rather than
>> uh... Conforming it to xcode 4.2's available settings until it built,
>> I manually converted it. This is embarrassing to admit, but at the
>> time I was so wrapped up in getting this app working, chasing bugs
>> and trying to have it submittable by the GM seed (which I missed by a
>> damn site.. thanks useless assembly language class I will never use
>> in life.) that I didn't really give much thought to reading the
>> "switching to" docs.
>
> This happens to everyone I think.
>
> But as I tried to make clear above, I was not talking about converting
> to Xcode 4.2, or to ARC, or to armv7, but particularly about converting
> to a universal (iPhone/iPad) app.
Well yeah as I said above, I just took the iPhone project since it had the most updated code (I had been doing everything for the phone first then adding the new code in to the iPad project.) Dragged all the iPad nibs in to it, created a target, and surrounded anything that required iPad handling with if(ISIPAD){ do this;} (ISIPAD is a macro I keep in a global header I include in every project.)
Basically I was trying to do things as quickly as possible so I could get back to the business of actually making the app in to what it always should have been rather than it's first poorly implemented incarnation.
>
>> Well with the app submitted and my motivation to learn cocos2d low...
>> Thats a long story that for the first time in 10 years has me
>> seriously considering trying to sell a project rather than complete
>> it. Anyway, I suppose it's time to catch up on the 4.2 docs and
>> "switching to" notes etc. I have 4 apps, two on the store, two in
>> development, that need updating/completion. Plus the app this thread
>> relates too already has a full plan for 3.1 laid out as well as
>> around 500 lines of commented code. (Things I skipped in order to get
>> it out the door.) It would be nice to not have to ask another dumb
>> question each time I start work on one of these. Besides, even with
>> months of 8+ hour days deep in the code, I just know that the
>> complete failure of iBetatest.com to produce anything useful, means
>> I've missed something somewhere in my testing and that of the 1
>> person that ever ran the app when I asked them to, and I am going to
>> have to fix a crash that never happened in all that time. After all,
>> those apple people could find a bug in 'hello world.'
>
> Between ARC and the static analyzer, a great many crashers can nowadays
> be eliminated.
Yeah... The ARC conversion was... time consuming. Lets just say that at times I can be a tad lazy about forward declarations and type casting when using things declared as id. Plus the app uses a lot of toll free bridges.
It was worth it... Since converting to ARC, memory usage dropped significantly. (Usually around 65 - 75 megs) and virtually all crashes stopped. (Not that there were that many by the time I did the conversion.) Of course the app can still run the phone out of memory and requires a lot of processor time.
>
> As for the task of finding good, reliable beta testers... if you figure
> out a secret, please don't keep it to yourself!
Certainly! right now all I can say for sure is that my experience with iBetaTest.com was very bad and I do not plan to revisit them. At least not in it's current incarnation.
April.
>
> --
> Conrad Shultz
>
> Synthetiq Solutions
> www.synthetiqsolutions.com
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden