Reconstruction of the Folios Android

Hello, I'm looking for suggestions on the workflow for Android 7 '' tablet. We currently have applications in both iTunes store GooglePlay (and Amazon). So far, I had used 1024 x 768 to build folios between all devices. However, we have just bought a Google Nexus 7 and downloaded our app only to discover that our folios are unreadable due to the proportion 4:3 and 3:2. I would like to rebuild our folios for the Android Tablet but since they are already published I do not know where to start.

If I take the approach of 'Lazy Susan' by Bob #1 scenario (referring to article "creating DPS Folios for Android devices") and reuse my iPad and do documents a size of 1600 x 1200, would I need to:

(1) do not publish and then republish the folio?

(2) is it a good idea to reuse the the same publication ID?

(3) if so, what happens to the version from Amazon?

(4) does it matter if I decide to do a 'V' guidance document only when it was previously the two?

(5) will be the user then download the folio 'new' and delete/Archives of the folio published previously?

I guess if I choose to either go "all the way" and/or "Sensible shortcuts", these two processes would have the same questions (don't not publish/republish, etc..) I think it's good to add "renditions" at this stage because it is ' sort of ' a 'new '... Is this correct?

Any help would be appreciated. Thank you.

If you looked at your application on a larger HD Android tablet, you'd be even more disappointed what looks like your folio of 1024 x 768. It looks like a small stamp in the middle of a black screen. It is the big drawback of the 'Lazy Susan' approach, at least for now. (In a future release, Android viewers should be able to evolve the contents upwards or downwards. That will simplify things, and I need to revise my orientation.)

(1) there is no reason to not publish/republish the folio No. Simply create a new format 1600 x 1200 using the eponymous Folio, ID and product Date of Publication settings used in the folio of 1024 x 768. Of course, the problem with this approach is that 1600 x 1200 is still 4:3 aspect ratio, which does not look great on the 16:9 aircraft - ish. Consider creating 1280 x 800 for the Android source files and re-use for each rendition.

(2) what do you mean by reusing the same "publication ID"? If you mean using the same ID of role/title Application for iOS and Android, yes you can, but it often complicates things. It is generally easier to create separate accounts (title IDs) for iOS and Android. If you mean something else by "publication ID", please specify.

(3) the Amazon version should be fine, unless you have activated strict refunds (which you don't want to do in your case). Still, I can't understand the question.

(4) it is not a problem to create a folio double orientation for rendering and a folio of single-direction for another interpretation.

(5) which is a little tricky. If a user has already opened the application, the spectator is part rendering of 1024 x 768 and unfortunately does not check for a rendering again until the application itself in uninstalled/reinstalled.

Regarding your question on the addition of "renditions" at this point, that's perfectly fine. Addition of "renditions" doesn't hurt existing users, and this makes things better for your new users.

The key to success is to make sure that you configure your source files, so that they can be easily imported. Most of the editors take the road to "Shortcuts" sensible and create different renditions based on two or three sets of source files.

Tags: Digital Publishing Suite

Similar Questions

  • Creation of the folios for Android

    Dear Adobe community,

    before this started, I get:

    • I'm using InDesign CS6 Digital Publishing Suite,
    • running on a Professional subscription
    • and I'm not a native speaker. So please take pity with me ;-)


    Some time ago, I created ten folios through an application multi-folio with in-app purchases for the Apple iStore, ran into some issues (which have been resolved by Bob Bringhurst, thank you once again) and now I want to develop for Android. The creation itself was easy, that slips are already online, but do not without falling on key issues.

    To define my problem:

    • The splash screen does not. Only, it takes as much space as possible and grows around a third of the screen. Is there a "fit screen" - box, I missed?
    • The graphics look "rough", naked pixels in a sort of 8-bit-look without the edges soft (or feathers), even if they are PDF. I can't convert them to JPEG format, because I use the same folios as I do for Apple.
    • The effects of the erasure of all overlays are also rough. Slide shows, for example, are punching through their content, without letting that images fade out in the next. Maybe it's important to mention: they were created through the slide show option in the Folio Overlay-menu. The same problem occurs with all the contents that appear and disappear. For example: If you activate a card with a button (i.e. telling the app, to pass the object to the empty state 1 in filled State 2), the application takes one second and the map appears hard, smashing into the window from one moment to another, without the bland smooth as it does on Apple products.
    • And after some time, a minute or two, the application crashes, leaving the customer blocked for a moment, before him eject to the main screen of his camera.

    So far, this is my problem. Honestly, I feel that I missed a few easy step, but necessary for the expansion of Android. Now, the look of folios as some pre-pre-alpha release an Android (with dull graphics and blocks every 60 seconds), while they work fine and smooth on Apple.

    I would be grateful for any advice.

    BIS denn of Germany,

    Maximilian

    This article should help:

    Digital Publishing Suite help | Development of DPS native apps for Android devices

    Depending on your content, you can use a different account for your Android application.

  • Folios of detail does not show in the native Android Viewer

    > when I update the account application adding the secret sharing android I have to re - publish fact sheets to see in the library of Android?

    Do not republish folios.

    Sorry Neil, I have the Android native app ready to publish and activated (with the same id of iOS) in-app purchase of my folio of detail (Yes, it is published).

    On iOS, I see the folio of detail + another free folio, on Android, I see only the free folio.

    The private key is copied to the account id title (and then I have connection in the DPS dashboard with the id of title).

    And the Account of Google Merchant is verified and confirmed this morning.

    What do you think?

    Neil! I resolve - now I'll teach you a thing

    If you are not connected with a Google account in the store to play your folio of detail are hiddennnnn!

    *: I drink a lot of wine tonight

  • How is the best way to create a folio Android?

    I currently have the Enterprise edition of the DPS, and I have published 5 editions of my iPad app. I want to make one for Android. What is the best way to go about it.

    Can I creat a new folio? (When I do it does not give me an Android default size)

    What is the best size?

    Can I create by replacing using my iPad articles and put them in my new folio Android?

    What is the default format (PDF, PNG)?

    How can I create Android certificates?

    Any help would be greatly appreciated.

    Kind regards

    Michelle

    Create folios of 1024 x 768 or 1280 x 800 and allow content to scale. Test your content on Android devices.

    Android items:

    http://helpx.Adobe.com/Digital-Publishing-Suite/help/creating-documents-multiple-devices.h tml

    https://blogs.Adobe.com/indesigndocs/2012/10/creating-DPS-folios-for-Android-devices.html

    http://helpx.Adobe.com/Digital-Publishing-Suite/help/differences-iOS-Android-viewers.html

    http://helpx.Adobe.com/Digital-Publishing-Suite/KB/publishing-process-Android-Amazon-Mobil.html

  • How to prepare the folio for prior approval from Apple, but not visible on Android?

    Quite possible I just forget something, but it doesn't make sense to me. We have already active application in the App Store and the Google game, with a lot of questions for sale. Now we must prepare a special issue, which will go on sale next week or something like that. So I want to prepare the purchase app for prior approval. Now, we do not have full Folio, just one with a dummy cover.

    Workflow according to the guidelines of the guide to publication is:

    -make public and retail folio

    -submit the purchase app from Apple

    - and wait.

    I did it.

    OK, but what about Android? I even created in-app purchase in google play, set the correct product ID and set as unique, but I still see this dummy folio on Android. I can't buy it, but I see it, and it's not good.

    So how to solve this problem?


    Thanks for the quick help!

    Martin, I've confirmed this with a tester. He said, 'on Android (Google Play), the customer will see all public folios because Google does not provide an API to check what is available for purchase on their servers. On Amazon AppStore applications, the folio must not be visible. »

  • Reloading items in a Folio Android

    Hello

    On iOS, we triple click on a header to a folio that located on the Panel top nav to reload all the items (accordingly that all items starting from the first page).  Apparently the thing with the header does not work for Android. Question is how we can reload items in "folio" Android? I mean without the buttons dedicated inside articles. Is this possible?

    This is not possible with Android (or Windows) viewers with Digital Publishing Suite. In 2015, DPS, you can build an application and set on each collection if you want the playback position of items to remember. If you need to disable the memory of reading position I suggest creating an application of DPS 2015 instead.

    Neil

  • Is it possible to use < input type = file > in "folio" android?

    Hello

    I have a composed folio HTML article, where the user can change his image. To do this I use < input type = file >.

    and javascript of the api file. Everything works very well on iPads, iPhones and android browsers. But when this HTML code is

    placed inside folio adndroid, it is not working. Touch the input element does not bring the window 'choose file '. It doesn't do anything.

    I tested it on various devices adroid and versions of the system. I use the latest Adobe Content Viewer (32.5.3).

    This is limitation of folio android?

    See you soon.

    Unfortunately we do not support this type of input on Android.

    Neil

  • For iOS, ipad version shows the folio that was released, but the iPhone is not.

    I am responsible for managing the applications and not at all involved with or know how the process of creation of folio works.

    When I build the app for iOS, iPad version shows the folio that was released, but the iPhone does not show the folio.

    Is it something about the build process or how the folio was created?


    The folio also appears in the Android app (at least the phone I tested with).


    Thank you

    "Android and iOS viewers have different requirements for the display of the folios. Any size of folio you create can appear in a viewer for Android. Items are put on the scale and Letterbox if necessary. However, on the iPad, the Viewer displays only the folios with a 4:3 aspect ratio. IPhone Viewer displays only the folios with an aspect ratio 3:2 or 16:9 (1136 x 640). »

    Here is the post in full, if you want to learn more: Digital Publishing Suite help | Creating documents for multiple devices

  • Change the application android version

    Hello!

    How to change an application android version in folio Builder? I need to update the application to v31 and I can't see the option.

    Thank you!

    You use the web app builder to http://appbuilder.digitalpublishing.acrobat.com/? If so then all you have to do is:

    (1) select your existing application from the list, and then click the button change

    2) click on the next button until you get to the last page and then click on submit

    This will rebuild your app and automatically upgrade to the latest version (v31.1)

    If you use the builder desktop client application to build a legacy application there is no rejection v31. We stopped updating the legacy Android Viewer after exit 29. You must rather build a new native Android Viewer using the link above.

    Neil

  • Problems with rendering shadows and gradients in folios Android

    Does anyone have experience or solutions on how to solve a problem with damaged feathers, transparency and shadows in the "renditions" Android/folios?

    In the interpretation of the iPad (1024 x 768), there are several frames scrollables, multi-state objects with transparencies and gradients etc. When it is seen on Android devices, if specific rendering of the iPad or Android rendered, it restores transparency, gradients and shadows as a white tone and that he is not rich somehow.

    Is this a known problem or there at - there a way around this?

    Is this problem resolved when you change vector to Raster (or vice versa)?

    Edit: To add a color to this, we have an old bug that we decided to not no difficulty last year titled: "Display of MSO with transparency applied is different with 'Pixelated' and 'Signifying' at the discretion of MSO." Looking at the details of this bug, it seems to be exactly what you are light (whiteness in transparency on vector), so I hope that my question above translates a work around.

    Thank you

    Dave

  • Transfer of the DPS Android app

    Hello!

    Is it possible to transfer the DPS Android app to the SD card and then run it on another device?

    What is the possibility to copy and distribute the DPS of detail folio apps on Android?

    Ah! At this moment, we support download of internal storage. We have plans to add support for storage on external storage, but we did not yet work.

    The only requirement is Android 4.0.3 or later.

    Neil

  • You can create an application using Adobe DPS, then go the Folio to a programmer to add interactivity?

    I would like to know if I can create an application using Adobe DPS, Col. of the folio to a programmer to add advanced interactivity which does not DPS. I would like to the programmer to use XCode or Android SDK because it is a standard, but they can also use c#, JavaScript and many other coding languages. Folio would serve the purpose of a waterproof digital mock-up for the programmer.

    DPS is very extensible using HTML, but the folios can be cracked open

    to add to.

  • Have the folio version influence on performance?

    It is fairly theoretical question, but who knows .

    For compatibility, we mainly use the folio format 20. Can there be a difference in performance, when we will use with 24/25 player ever version of the folio? Than ever folio format will be faster, for example. I would like to know this for iPad and Android, because it bothers me more on Android (even on the new fast device experience is subpar compared to the iPad).

    Thank you

    It depends largely on the features you use. That said, if you can update your applications v24 to v25, I think that it is best to do, especially for Android applications. If you are creating Android applications, v25 folios work better the range of Android devices. To see if you want to use v24 or v25, look for differences between the two libraries.

    You can look at the history of what the news to see what is applied since the v20.

  • How the folio pricing structure does not work if you design for the corporate world

    Hi in my world I'm not selling my Apps but their production for customers who need to turn to download for free because they are Corporate Brochures and newsletters and free guides.

    Then... If I buy the large single version of research free cloud and produce a brochure/portfolio should I notify my customer that they must pay these costs of bundle folio on top for their audience to download?   17 p has download?

    I can see he said the folio is free but do they really mean it I fear just don't to the land of my client with hidden costs.

    If I move to professional, that would mean I could publish to androids large but why make it difficult for small agencies and let them only able to offer ipad apps it's crazy!

    Folio unique means a brochure or a single download of this free booklet with one of the two packages.  I spent 3 hours looking for the answer I'm missing something!

    I hope someone can help it's superb but if 10,000 people download my free brochure of customers it could cost more than traditional printing? Is there a blocker which if it became merit to be published and downloaded at 1 million people is there a ceiling to stop it being downloaded?

    It feels like a mobile phone price list!

    If you want to create one question app you can buy subscription CCM in which you can create apps one unlimited question. In CCMS, you can create app for ipad, not for the iphone and the andfroid. In CCM you need not to buy the bundle download .folio. Only paid subscription fees.

    If you are targeting Android and ipad & iphone, then recommend you buy DPS Professional Edition or Enterprise edition. In the present, you can create apps for one question and several questions. Professional DPS is also a monthly and annual subscription. This will include 5000 (annual) and files monthly .folio (250) with the first year of service. Once files .folio exhausted, you can buy additional group at any time on the Adobe store or reseller. Platform to pay US$ 495 monthly and annual cost you US$ 5 940.

    Here is the link where you can compare the features and price of all three edition of DPS:

    http://www.Adobe.com/products/Digital-Publishing-Suite-family/buying-guide-pricing.html

    For more details, you can always contact sales 877-792-3623 DPS

  • Folio Android questions

    Hi all

    I'm having some problems with getting my magazine working on Android devices

    1. the Google play Store: I created an application for this store. It works on shelves very well, but I can't make it appear on mobile phones. I thought that the Android system would automatically resize/scale. In the shop Google it is said in the manifesto that my application is just implemented for screens "large/xlarge.

    I do a smaller rendering in order to get the app to appear for normal/small screens as well? Or their something I do is wrong while I do the app in app Builder. It seems I'm doing something wrong in the application Builder because it's the only way I think that it identifies the clear info?

    2 kindle Fire: problems with the Amazon with the Kindle store. Of the same folio which pulls up the shop Google works very well on the Kindle (which is good). The problem I have is that the iPhone version of the app also makes its appearance in the library. I can't understand why this is as follows. I guess its because of the size of the folio (960 x 640). I can download this version of the iPhone, but I can't see it as it was made in PDF format.

    I think I need to do 1 of 2 things, but I would like to know if anyone has a solution before I rebuild the whole magazine.

    I must:

    R: rebuild the application iPhone as a PNG so that when the Kindle gets folio it works? The thing that that worries me is that it will take 2 sheets of the same content for download.

    B: create a new Adobe ID, and then create a new application that pulls this account Android folios. This would eliminate cross-contamination of the folios Apple and this seems to be the easiest of the fix.

    If anyone has another way to correct or to address this problem, I'd appreciate it.

    DPS apps appear only on the Large or XLarge Android tablets. Android phones are not yet supported.

    I don't know why your iPhone "renditions" are appearing on your Android devices. Perhaps rendering is not configured correctly. Nevertheless, I learned the hard way that it is better to use different for iOS and Android apps applications accounts, unless you set up custom payment.

    For more information on the problems of Android, see this article:

    http://blogs.Adobe.com/indesigndocs/2012/10/creating-DPS-folios-for-Android-devices.html

Maybe you are looking for