White Rose Photo Editor is an Android Personalization app that is developed by Run Photo Editor and published on Google play store on NA. It has already got around 1000 so far with an average rating of 4.0 out of 5 in play store.
White Rose Photo Editor requires Android OS version of 3.4 and up. Also, it has a content rating of Everyone from which one can decide if it is suitable to install for family, kids or adult users.
Since White Rose Photo Editor is an Android app and cannot be installed on Windows PC or MAC directly, we will show how to install and play White Rose Photo Editor on PC below:
Find games for macOS tagged Beat 'em up like EGGNOGG+, ★FROG SMASHERS★, Street Fighter Online, Zero Deaths, Tonight We Riot on itch.io, the indie game hosting marketplace. Reported a rise of 744% OS X malware over 2015 in 2016 5. The increasing Mac OS X market size (second after Microsoft Windows 6 and its fast adoption rate motivate cyber threat actors to shift their focus to developing OS X malware. The 'myth' that OS X is a more secure system only further increases malware success rate.
- Firstly, download and install an Android emulator to your PC
- Download White Rose Photo Editor APK to your PC
- Open White Rose Photo Editor APK using the emulator or drag and drop the .APK file into the emulator to install the app. OR
- If you do not want to download the .APK file you can still run White Rose Photo Editor PC by connecting or configuring your Google account with the emulator and downloading the app from play store directly.
If you follow the above steps correctly, you should have the White Rose Photo Editor app ready to run on your Windows PC or MAC.
Alias for the frame_screenshots action
System 7, codenamed 'Big Bang', and also known as Mac OS 7, is a graphical user interface-based operating system for Macintosh computers and is part of the classic Mac OS series of operating systems. It was introduced on May 13, 1991, by Apple Computer, Inc. 1 It succeeded System 6, and was the main Macintosh operating system until it was.
Easily put your screenshots into the right device framesframeit allows you to put a gorgeous device frame around your iOS, macOS and Android screenshots just by running one simple command. Use frameit to prepare perfect screenshots for the App Store, your website, QA or emails.
Features • Usage • Tips
frameit is part of fastlane: The easiest way to automate beta deployments and releases for your iOS and Android apps.
Frame screenshot
Put a gorgeous device frame around your iOS, macOS and Android screenshots just by running one simple command. Support for:
- iPhone, iPad and Mac
- Set of Android devices
- Portrait and Landscape modes
- Several device frame colors
The complete and updated list of supported devices and colors can be found here
Here is a nice gif, that shows frameit in action:
Advanced Features
- Put framed screenshot on colored background, define padding
- add text above or under framed screenshot
- keyword + text
- choose text font and color
- multi line text
- 'intelligent' positioning of text that always looks good(ish)
Results
The frameit 2.0 update was kindly sponsored by MindNode, seen in the screenshots above.
The first time that frameit is executed the frames will be downloaded automatically. Originally the frames are coming from Facebook frameset and they are kept on this repo.
More information about this process and how to update the frames can be found here
Basic Usage
Why should you have to use Photoshop, just to add a frame around your screenshots?
Just navigate to your folder of screenshots and use the following command (iOS and Mac OS are default platforms for backward compatibility):
To frame Android screenshots:
To use the silver version of the frames:
To download the latest frames
Note: When using frameit without titles on top, the screenshots will have the full resolution, which means they can't be uploaded to the App Store directly. They are supposed to be used for websites, print media and emails. Check out the section below to use the screenshots for the App Store.
Advanced Usage (optional)
Text and Background
With frameit it's possible to add a custom background and text below or above the framed screenshots in fonts and colors you define.
A working example can be found in the fastlane examples project.
Framefile.json
The Framefile allows to define general and screenshot specific information.It has the following general JSON structure:
General parameters
The general parameters are defined in the default key and can be:
| Key | Description | Default value |
|---|---|---|
background | The background that should be used for the framed screenshot. Specify the (relative) path to the image file (e.g. *.jpg). This parameter is mandatory. | NA |
keyword | An object that contains up to 3 keys to describe the optional keyword. See table below. | NA |
title | An object that contains up to 3 keys to describe the mandatory title. See table below. | NA |
stack_title | Specifies whether frameit should display the keyword above the title when both keyword and title are defined. If it is false, the title and keyword will be displayed side by side when both keyword and title are defined. | false |
title_below_image | Specifies whether frameit should place the title and optional keyword below the device frame. If it is false, it will be placed above the device frame. | false |
show_complete_frame | Specifies whether frameit should shrink the device frame so that it is completely shown in the framed screenshot. If it is false, clipping of the device frame might occur at the bottom (when title_below_image is false) or top (when title_below_image is true) of the framed screenshot. | false |
padding | The content of the framed screenshot will be resized to match the specified padding around all edges. The vertical padding is also applied between the text and the top or bottom (depending on title_below_image) of the device frame. There are 3 different options of specifying the padding: 1. Default: An integer value that defines both horizontal and vertical padding in pixels. A combination of option 2 and 3 is possible, e.g. | 50 |
interline_spacing | Specifies whether frameit should add or subtract this many pixels between the individual lines of text. This only applies to a multi-line title and/or keyword to expand or squash together the individual lines of text. | 0 |
font_scale_factor | Specifies whether frameit should increase or decrease the font size of the text. Is ignored for keyword or title, if font_size is specified. | 0.1 |
frame | Overrides the color of the frame to be used. (Valid values are BLACK, WHITE, GOLD and ROSE_GOLD) | NA |
title_min_height | Specifies a height always reserved for the title. Value can be a percentage of the height or an absolute value. The device will be placed below (or above) this area. Convenient to ensure the device top (or bottom) will be consistently placed at the same height on the different screenshots. | NA |
use_platform | Overrides the platform used for the screenshot. Valid values are IOS, ANDROID and ANY. | IOS |
force_device_type | Forces a specific device. Valid values are: Huawei P8, Motorola Moto E, Motorola Moto G, Nexus 4, Nexus 5X, Nexus 6P, Nexus 9, Samsung Galaxy Grand Prime, Samsung Galaxy Note 5, Samsung Galaxy S Duos, Samsung Galaxy S3, Samsung Galaxy S5, Samsung Galaxy S7, Samsung Galaxy S8, Samsung Galaxy S9, iPhone 5s, iPhone 5c, iPhone SE, iPhone 6s, iPhone 6s Plus, iPhone 7, iPhone 7 Plus, iPhone 8, iPhone 8 Plus, iPhone X, iPhone XS, iPhone XR, iPhone XS Max, iPad Air 2, iPad Mini 4, iPad Pro, MacBook, Google Pixel 3, Google Pixel 3 XL, HTC One A9, HTC One M8 | NA |
Specific parameters
The screenshot specific parameters are related to the keyword and title texts.These are defined in the data key. This is an array with the following keys for each screenshot:
| Key | Description |
|---|---|
filter | This is mandatory to link the individual configuration to the screenshot, based on part of the file name. Example: |
keyword | Similar use as in default, except that parameter text can be used here because it is screenshot specific. |
title | Similar use as in default, except that parameter text can be used here because it is screenshot specific. |
frame | Overrides the color of the frame to be used. (Valid values are BLACK, WHITE, GOLD and ROSE_GOLD) |
use_platform | Overrides the platform used for the screenshot. Valid values are IOS, ANDROID and ANY. |
force_device_type | Forces a specific device. Valid values are the same as for the general parameter. |
Framefile keyword and title parameters
The keyword and title parameters are both used in default and data. They both consist of the following optional keys:
| Key | Description | Default value |
|---|---|---|
color | The font color for the text. Specify a HEX/HTML color code. | #000000 (black) |
font | The font family for the text. Specify the (relative) path to the font file (e.g. an OpenType Font). | The default imagemagick font, which is system dependent. |
font_size | The font size for the text specified in points. If not specified or 0, font will be scaled automatically to fit the available space. frameit still shrinks the text, if it would not fit. | NA |
font_weight | The font weight for the text. Specify an integer value (e.g. 900). | NA |
text | The text that should be used for the keyword or title. Note: If you want to use localised text, use | NA |
Example
You can find a more complex configuration to also support Chinese, Japanese and Korean languages.
The Framefile.json should be in the screenshots folder, as seen in the example.
White Rose (demo) Mac Os X
.strings files
To define the title and optionally the keyword, put two .strings files into the language folder (e.g. en-US in the example project)
The keyword.strings and title.strings are standard .strings file you already use for your iOS apps, making it easy to use your existing translation service to get localized titles.
Notes
White Rose (demo) Mac Os Catalina
To download the latest frames
Note: When using frameit without titles on top, the screenshots will have the full resolution, which means they can't be uploaded to the App Store directly. They are supposed to be used for websites, print media and emails. Check out the section below to use the screenshots for the App Store.
Advanced Usage (optional)
Text and Background
With frameit it's possible to add a custom background and text below or above the framed screenshots in fonts and colors you define.
A working example can be found in the fastlane examples project.
Framefile.json
The Framefile allows to define general and screenshot specific information.It has the following general JSON structure:
General parameters
The general parameters are defined in the default key and can be:
| Key | Description | Default value |
|---|---|---|
background | The background that should be used for the framed screenshot. Specify the (relative) path to the image file (e.g. *.jpg). This parameter is mandatory. | NA |
keyword | An object that contains up to 3 keys to describe the optional keyword. See table below. | NA |
title | An object that contains up to 3 keys to describe the mandatory title. See table below. | NA |
stack_title | Specifies whether frameit should display the keyword above the title when both keyword and title are defined. If it is false, the title and keyword will be displayed side by side when both keyword and title are defined. | false |
title_below_image | Specifies whether frameit should place the title and optional keyword below the device frame. If it is false, it will be placed above the device frame. | false |
show_complete_frame | Specifies whether frameit should shrink the device frame so that it is completely shown in the framed screenshot. If it is false, clipping of the device frame might occur at the bottom (when title_below_image is false) or top (when title_below_image is true) of the framed screenshot. | false |
padding | The content of the framed screenshot will be resized to match the specified padding around all edges. The vertical padding is also applied between the text and the top or bottom (depending on title_below_image) of the device frame. There are 3 different options of specifying the padding: 1. Default: An integer value that defines both horizontal and vertical padding in pixels. A combination of option 2 and 3 is possible, e.g. | 50 |
interline_spacing | Specifies whether frameit should add or subtract this many pixels between the individual lines of text. This only applies to a multi-line title and/or keyword to expand or squash together the individual lines of text. | 0 |
font_scale_factor | Specifies whether frameit should increase or decrease the font size of the text. Is ignored for keyword or title, if font_size is specified. | 0.1 |
frame | Overrides the color of the frame to be used. (Valid values are BLACK, WHITE, GOLD and ROSE_GOLD) | NA |
title_min_height | Specifies a height always reserved for the title. Value can be a percentage of the height or an absolute value. The device will be placed below (or above) this area. Convenient to ensure the device top (or bottom) will be consistently placed at the same height on the different screenshots. | NA |
use_platform | Overrides the platform used for the screenshot. Valid values are IOS, ANDROID and ANY. | IOS |
force_device_type | Forces a specific device. Valid values are: Huawei P8, Motorola Moto E, Motorola Moto G, Nexus 4, Nexus 5X, Nexus 6P, Nexus 9, Samsung Galaxy Grand Prime, Samsung Galaxy Note 5, Samsung Galaxy S Duos, Samsung Galaxy S3, Samsung Galaxy S5, Samsung Galaxy S7, Samsung Galaxy S8, Samsung Galaxy S9, iPhone 5s, iPhone 5c, iPhone SE, iPhone 6s, iPhone 6s Plus, iPhone 7, iPhone 7 Plus, iPhone 8, iPhone 8 Plus, iPhone X, iPhone XS, iPhone XR, iPhone XS Max, iPad Air 2, iPad Mini 4, iPad Pro, MacBook, Google Pixel 3, Google Pixel 3 XL, HTC One A9, HTC One M8 | NA |
Specific parameters
The screenshot specific parameters are related to the keyword and title texts.These are defined in the data key. This is an array with the following keys for each screenshot:
| Key | Description |
|---|---|
filter | This is mandatory to link the individual configuration to the screenshot, based on part of the file name. Example: |
keyword | Similar use as in default, except that parameter text can be used here because it is screenshot specific. |
title | Similar use as in default, except that parameter text can be used here because it is screenshot specific. |
frame | Overrides the color of the frame to be used. (Valid values are BLACK, WHITE, GOLD and ROSE_GOLD) |
use_platform | Overrides the platform used for the screenshot. Valid values are IOS, ANDROID and ANY. |
force_device_type | Forces a specific device. Valid values are the same as for the general parameter. |
Framefile keyword and title parameters
The keyword and title parameters are both used in default and data. They both consist of the following optional keys:
| Key | Description | Default value |
|---|---|---|
color | The font color for the text. Specify a HEX/HTML color code. | #000000 (black) |
font | The font family for the text. Specify the (relative) path to the font file (e.g. an OpenType Font). | The default imagemagick font, which is system dependent. |
font_size | The font size for the text specified in points. If not specified or 0, font will be scaled automatically to fit the available space. frameit still shrinks the text, if it would not fit. | NA |
font_weight | The font weight for the text. Specify an integer value (e.g. 900). | NA |
text | The text that should be used for the keyword or title. Note: If you want to use localised text, use | NA |
Example
You can find a more complex configuration to also support Chinese, Japanese and Korean languages.
The Framefile.json should be in the screenshots folder, as seen in the example.
White Rose (demo) Mac Os X
.strings files
To define the title and optionally the keyword, put two .strings files into the language folder (e.g. en-US in the example project)
The keyword.strings and title.strings are standard .strings file you already use for your iOS apps, making it easy to use your existing translation service to get localized titles.
Notes
White Rose (demo) Mac Os Catalina
- These
.stringsfiles MUST be utf-8 (UTF-8) or utf-16 encoded (UTF-16 BE with BOM). They also must begin with an empty line. If you are having trouble see issue #1740 - You MUST provide a background if you want titles. frameit will not add the titles if a background is not specified.
Screenshot orientation
By default frameit adds a frame to your screenshot based on an orientation you took it. For a portrait (vertical orientation) it is going to add portrait frame and for a landscape (horizontal orientation) - landscape left (= Home button on the left side).
One way to override the default behavior is editing the file name by adding force_landscaperight to the end.
force_orientation_block
If the default behavior doesn't fit your needs and you don't want or can't rename your screenshots, you can customize frameit's orientation behavior by setting a force_orientation_block parameter. The valid values are: :landscape_left (home button on the left side), :landscape_right (home button on the right side), :portrait (home button on the bottom), nil (home button on the right side).
Examples
With frameit it's possible to also frame macOS Application screenshots. You have to provide the following:
- A (relative) path to a
backgroundimage file, which should contain both the background and the Mac. - The
offsetinformation so frameit knows where to position your screenshot on thebackground:offset: A string that specifies the horizontal and vertical offset in pixels, with respect to the top left corner of thebackgroundimage. The syntax is'++', e.g.'+200+150'.titleHeight: The height in pixels that should be used for the title.
Example
Check out the MindNode example project.
Generate localized screenshots
Check out snapshot to automatically generate screenshots using UI Automation.
Resume framing
Framing screenshots is a slow operation. In case you need to resume framing, or just frame a couple updated screenshots again, you can rely on the --resume flag. Only screenshots which have not been framed yet – or for which there isn't an up-to-date framed image – will be framed. This feature uses the file modification dates and will reframe screenshots if the screenshot is newer than the framed file.
Upload screenshots
Use deliver to upload iOS screenshots to App Store Connect, or supply to upload Android screenshots to Play Store completely automatically 🚀
Use a clean status bar
You can set override_status_bar to true in snapshot to set the status bar to Tuesday January 9th at 9:41AM with full battery and reception.
Gray artifacts around text
If you run into any quality issues, like having a border around the font, it usually helps to just re-install imagemagick. You can do so by running
Uninstall
gem uninstall fastlanerm -rf ~/.frameit
| frameit | |
|---|---|
| Supported platforms | ios, android, mac |
| Author | @KrauseFx |
6 Examples
Parameters
| Key | Description | Default |
|---|---|---|
white | Use white device frames | |
silver | Use white device frames. Alias for :white | |
rose_gold | Use rose gold device frames. Alias for :rose_gold | |
gold | Use gold device frames. Alias for :gold | |
force_device_type | Forces a given device type, useful for Mac screenshots, as their sizes vary | |
use_legacy_iphone5s | Use iPhone 5s instead of iPhone SE frames | false |
use_legacy_iphone6s | Use iPhone 6s frames instead of iPhone 7 frames | false |
use_legacy_iphone7 | Use iPhone 7 frames instead of iPhone 8 frames | false |
use_legacy_iphonex | Use iPhone X instead of iPhone XS frames | false |
use_legacy_iphonexr | Use iPhone XR instead of iPhone 11 frames | false |
use_legacy_iphonexs | Use iPhone XS instead of iPhone 11 Pro frames | false |
use_legacy_iphonexsmax | Use iPhone XS Max instead of iPhone 11 Pro Max frames | false |
force_orientation_block | [Advanced] A block to customize your screenshots' device orientation | * |
debug_mode | Output debug information in framed screenshots | false |
resume | Resume frameit instead of reprocessing all screenshots | false |
use_platform | Choose a platform, the valid options are IOS, ANDROID and ANY (default is either general platform defined in the fastfile or IOS to ensure backward compatibility) | * |
path | The path to the directory containing the screenshots | * |
* = default value is dependent on the user's system
Documentation
To show the documentation in your terminal, run
CLI
It is recommended to add the above action into your Fastfile, however sometimes you might want to run one-offs. To do so, you can run the following command from your terminal
To pass parameters, make use of the : symbol, for example
It's important to note that the CLI supports primitive types like integers, floats, booleans, and strings. Arrays can be passed as a comma delimited string (e.g. param:'1,2,3'). Hashes are not currently supported.
It is recommended to add all fastlane actions you use to your Fastfile.
Source code
This action, just like the rest of fastlane, is fully open source, view the source code on GitHub
