White labeling an app

[Nic Wise]

eg I have an app, and someone wants a custom version of it - seperate
app in the appstore, some basic customizations (color mostly) etc.

I was thinking about doing it with 2 SLN's / csproj's, and just keep
those in sync., kinda like DropNet or RestSharp does.

Anyone done it? Advice?

--
Nic Wise
t.  +44 7788 592 806 | @fastchicken | http://www.linkedin.com/in/nicwise
b. http://www.fastchicken.co.nz/ | http://www.flickr.com/photos/nicwise

mobileAgent (for FreeAgent): get your accounts in your pocket.
http://goo.gl/IuBU
Trip Wallet: Keep track of your budget on the go: http://goo.gl/ePhKa
London Bike App: Find the nearest Boris Bike, and get riding! http://goo.gl/Icp2

[ManniAT Pohler]

In general I do this using 2 csproj's linking the "common" files.
I don't know it MT supports this - but in VS (I use VS for development) I can say "open file" and choose "link" from the open button.
 
Manfred
 

> Date: Fri, 17 Jun 2011 13:41:39 +0100
> Subject: White labeling an app
> From: ni...@fastchicken.co.nz
> To: mono...@googlegroups.com; mono...@lists.ximian.com

[Andreas Ploetzeneder]

We do something like that, with XML from a server. When app starts, we load the brand design,..with colors,...and so on :-)

2011/6/17 ManniAT Pohler <man...@live.com>

--

 

 

Mit freundlichem Gruß,

Andreas Plötzeneder
CEO
ihr ploetzeneder it-solutions Team
Mobile Development – Desktopanwendungen – Webanwendungen
Tel:  +43 720 30 30 24 10
Fax: +43 720 30 30 24 20
Email: in...@ploetzeneder-it.com
web:   http://www.ploetzeneder-it.com

Der Inhalt dieser E-Mail samt aller Anhänge ist vertraulich und ausschließlich für den Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sind, so löschen sie diese bitte und informieren Sie den Absender. Jede Form der Verbreitung oder Veröffentlichung der E-Mail, sei es in ihrer Gesamtheit oder in Teilen, die nicht ihrem Zweck dient, ist unzulässig. Das Internet kann die Unversehrtheit dieser Mitteilung nicht garantieren. ploetzeneder it-solutions übernimmt daher keine Haftung, falls die E-Mail geändert wurde.

 

[jon hopkins]

how do I get off this mailing list. it would be useful as a digest,
but not for every
single message.

no offence :-)

jon

[Nic Wise]

None taken. It's a google group, so start at groups.google.com - or
read the email it most likely sent you when you signed up.

[Nic Wise]

Thanks Craig, that gels with what I thought I had to do.

So far, I have a lot (all) of my constants moved out into another
class, so I just call one method on startup, and now it's label A, not
the normal one, which works nicely. The default.png will need to be
different, but thats ok - as you pointed out, I need to do a seperate
.csproj for the bundle ID, so I'll do the default in there too.

Cheers!

On Sun, Jun 19, 2011 at 00:33, Craig Dunn
<craig...@conceptdevelopment.net> wrote:
> Nic,
>
> for a variety of reasons (mainly the number of testers, and different types
> of testing - including "content" testing) we have three 'versions' of our
> app... purple, orange and green. They are effectively 'white label' along
> the lines you describe (different text, images, UIColors and accesses
> different back-end webservices).
>
> we do it with compiler directives (and some post-build 'custom commands' in
> MD)
>
> images references (ie the path) and customizable text are all in
> 'constants', which change based on the #if PREVIEW or #if DEBUG directives.
>
> we then create different build configurations that include/exclude the
> relevant compiler directives. the post-build command that exists in some
> builds to swap plists around looks like this http://twitpic.com/5di7mk
>
> for simplicity all test/debugging builds ships with ALL the images embedded,
> and the compiler directives just switch which ones are referenced. for
> appstore build there's a pre-build step to delete the unwanted image folders
> so they don't end up in the final .app
>
> the one thing we don't care about, but you would have to manage manually, is
> the BundleIdentifier set in Options-iPhone Application... while you can
> easily assign specific prov-profile/certs based on build configuration, the
> BundleIdentifier is 'hardcoded'... forgetting to change that would be a real
> pain!
>
> HTH
> Craig

>> _______________________________________________
>> MonoTouch mailing list
>> Mono...@lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/monotouch