My responses to your questions are inline below:
Within APPviewer is this going to be developed as a feature? Can a feature request be submitted for this?
+ I don't think anyone has ever requested this feature, so there are no plans to develop this feature. I'm happy to file a feature request for this with the understanding that our developers may choose not to develop it.
How can we force this behaviour when using the SDK? Can you please send me instructions on this please?
+ This falls outside of the scope of the Meridian SDK. A developer would need to use the iOS and Android SDKs to create this behavior.
Is it possible to use the both web-based and SDK interchangeably. I would like to create some parts of the app with the web-based editor and some on the SDK. Please let me know if this is possible.
+ I'd like to try to clarify something, because this is important. All Meridian-powered apps use the Meridian Editor. Regardless of whether it's a white-label or SDK app. The Meridian Editor is the tool that people use to create and host all of the content that is used by Meridian-powered apps. This includes: maps, pages, placemarks, events, routing, language translations, and others.
When a customer purchases Meridian, they have an option to develop their iOS and Android Meridian-powered apps in one of two ways:
White-label apps: These apps are based on the AppViewer codebase and reflect the standard Meridian app experience. AppViewer IS the SDK, essentially. The UI is standard and non-customizable, but the color scheme of the app can be customized.
SDK apps: When a customer wants complete control over the development of their app or even already has an app, they can use the Meridian SDK to implement the Meridian features they'd like to see in their app. But even apps using the Meridian SDK would use the Meridian Editor to create the content consumed by the Meridian SDK.
In short:
Meridian Editor: Content for white-label and SDK apps
SDK: The structure for both white-label and SDK apps
Does that make sense? It doesn't actually make sense to say that someone would use the Meridian SDK but not the Meridian Editor. It's simply impossible to separate the two.
I remember seeing a table that shows what configuration was available through the web-based editor and the SDK. I cannot find this now, but this table lead me to think that some features are not available when only using one.
+ I'd love to see this table. :) Again, it doesn't make sense to distinguish between the Meridian Editor and the SDK. They are inseparable.
Can you please provide me with the instructions for this [importing feeds]so I can go through this with my customer.
+ Fortunately, we have some documentation on this:
http://docs.meridianapps.com/article/292-adding-events
http://docs.meridianapps.com/article/357-getting-data-into-meridian
I hope this helps!
Cheers,
Shawn