The market definitely takes some time to properly update. I was able to link
to my app directly using the package name almost immediately, but it took
about a day for it to fully start showing up in searches for both the web
and devices. Give it some time and everything will start showing up.
Also
I remember thinking the same thing when I published my app.
I had the direct link to it so I could download it and give it out, but
it seemed like it took a day or two before it would actually show up in
search results.
Jonathan
On 7/31/2011 6:27 PM, John Murray wrote:
> Has anyone got any us
Has anyone got any useful experience on uploading tothe Android market which
they could share?
I have registered and paid my subs
I have uploaded the app plus simple description screenshots, high res icon
etc
In other words al non optional fields are complete and correct, this has
been saved and
MT and MD rely on their respective native UI layers, so they can't share UI
code. And code for interacting directly with the device APIs are unique to
each platform. However, data access, business logic, etc can be shared.
Craig Dunn (http://conceptdev.blogspot.com/) has written some good posts
Monotouch does support the iPad right now.
Sent from my iPhone
On Jul 31, 2011, at 1:30 PM, "Tim Kelly" wrote:
> I've decided to stick with Mono for Android in hopes of supporting iPad's.
> So here's my overall question:
>
>
>
> 1. How compatible is Mono for Android and MonoTouch?
>
>
I've decided to stick with Mono for Android in hopes of supporting
iPad's. So here's my overall question:
1. How compatible is Mono for Android and MonoTouch?
2. Does MonoTouch support the iPad?
If someone could shine a little knowledge on this I would appreciate it,
thanks.
Tim
Hello,
From the structural aspect...
I believe this Q should be first directed to android platform itself:
- At run time, Mono for Android basically runs on top of android
framework and apps are in dalvik VM bytecode. There is no
point that Java 7 affects here.
- Dalvik bytecode (dex) is
I am using arrayadapters for listviews on dialog boxes and for
autocomplettion
I have a few questions
1) I've found it far faster to have an array built in as a resource
than to load data from an xml using Linq
The array from resource ('bout 270 items) loads in under a second whereas
u
This are both great ideas.
Mono's strength is unifying the platforms. Playing nice with PhoneGap would be
a great first step I think.
Though ultimately I think a Silverlight View layer that can be built on all
major platforms would be ideal. Pretty much rewriting PhoneGap in
Silverlight/C#.
