You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adds 6 new devices that allow developers to take screenshots that conform to all the size and resolution requirements of the iOS and Android app stores:
iPhone 5.5" (1242x2208)
iPhone 6.5" (1242x2688)
iPad 12.9" (2048x2732)
Android 16:9 Phone (1242x2208)
Note: Same as iPhone 5.5"
Android 7" Tablet (1728x3072)
Android 10" Tablet (2160x3840)
Notes
The devices do not have any frames, since they only exist for screenshotting purposes. I used these devices to capture all the screenshots for my Flutter app and can confirm it produces the correct sizes/aspect ratios for both stores.
If you don't like the lack of frames, I could consider surrounding each with a generic black square (maybe with some text describing its purpose), if that would make sense.
I'm also open to any naming changes if you think these could be more clear. Ideally, I would have put all of these devices in their own category/tab (e.g. "App store screenshots"), but it appears the current categories are backed by a built-in enum, so I wasn't sure how to go about this.
Compliments
Thanks so much for putting this project together! It literally saved me hours. My app is a drawing app, so putting together a single screenshot-worthy drawing can take hours. Doing this 5 times for each screenshot was a total non-starter for me.
Also, the way this project uses the SVG files as input is brilliant!
This PR would be very nice to have. I am trying to produce App Store screenShots and I am missing:
iPhone· 6.5-inch
iPhone 8 Plus · 5.5-inch
iPad Pro (6th Gen) 12.9" Display
iPad Pro (2nd Gen) 12.9" Display
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Adds 6 new devices that allow developers to take screenshots that conform to all the size and resolution requirements of the iOS and Android app stores:
Notes
The devices do not have any frames, since they only exist for screenshotting purposes. I used these devices to capture all the screenshots for my Flutter app and can confirm it produces the correct sizes/aspect ratios for both stores.
If you don't like the lack of frames, I could consider surrounding each with a generic black square (maybe with some text describing its purpose), if that would make sense.
I'm also open to any naming changes if you think these could be more clear. Ideally, I would have put all of these devices in their own category/tab (e.g. "App store screenshots"), but it appears the current categories are backed by a built-in enum, so I wasn't sure how to go about this.
Compliments
Thanks so much for putting this project together! It literally saved me hours. My app is a drawing app, so putting together a single screenshot-worthy drawing can take hours. Doing this 5 times for each screenshot was a total non-starter for me.
Also, the way this project uses the SVG files as input is brilliant!
Closes #38
Closes #85