Overview
FlixBus sells intercity bus and train tickets across Europe, the Americas and beyond. Its site is drawn in Flix lime green and dark gray: a lime header, lime buttons with dark gray text, Roboto for everything and 6px corners almost everywhere. Search sits in one white bar on a cool blue-tinted band. [Observed]
What defines the look:
- Lime green with dark text.
#97d700fills the header, the Search button and Explore the map, always with#353535text, never white. [Measured] - Dark gray, not black.
#353535is the text color everywhere, with#444444and#646464for secondary text. [Measured] - Roboto only. Roboto at 400, 500 and 700, with bold 16px section headings rather than large ones. [Measured]
- 6px everywhere. Buttons, fields, nav items and icon frames use 6px corners. [Measured]
- Lime wash accents. Icon frames and the selected tab use a pale lime
#e5f9c0. [Measured]
Source for this file: the home page with its search bar, the London city page and a not-found page (the help address no longer exists), measured in a browser at 1440 and 390 wide on 2026-10-15, with a dark color scheme pass. The site redirected to its United States edition for the region we browse from. FlixBus's component library shows in the page markup, but its documentation is not public. Results and checkout were not measured. No app captures were used. See Known Gaps.
Core
Colors
| Role | Value | Where |
|---|---|---|
| Flix lime | #97d700 with #353535 text | Header, Search, Explore the map, Get the App [Measured] |
| Lime wash | #e5f9c0 | Icon frames, the selected Cities tab [Measured] |
| Text | #353535, #444444 | All text [Measured] |
| Muted text | #646464 | Helper text [Measured] |
| Link | #0047de | Inline links, the app download prompt [Measured] |
| Canvas | #ffffff | Search fields, cards [Measured] |
| Page | #f7f7f7 | Sections [Measured] |
| Search band | blue #016ae7 at 12 percent (about #e0edfc on white) | Behind the search bar [Measured] |
| Gray fill | #e1e1e1 | Panels [Measured] |
| Borders | #c8c8c8, #848484 | Fields and dividers [Measured] |
Typography
Roboto at 400, 500 and 700. [Measured]
| Role | Desktop | Mobile | Weight |
|---|---|---|---|
| Error title | 38 on 44 | 27.2 on 32 | 700 [Measured] |
| Hero | 34 on 40.8 | 22 on 26.4 | 700 [Measured] |
| Stat line | 32 on 48 | not measured | 700 [Measured] |
| City hero | 28 on 32 | not measured | 700 [Measured] |
| Title | 20.8 on 27.2 | not measured | 700 [Measured] |
| Section heading | 16 on 24 | same | 700 [Measured] |
| Body | 16 on 24 | 12 on 18 for feature notes | 400 [Measured] |
| Button and nav | 16 on 24 | same | 500 [Measured] |
Shape and spacing
6px is the house corner for buttons, fields, nav items and tiles, with 5 and 8 in a few places, 18 on one card and full pills for a few chips. [Measured] Buttons carry 5 to 8 by 12 padding, nav items 6 by 12 (18 by 12 in the 60 high header). [Measured]
Iconography and motion
Icons sit in 42px lime wash frames with a 6px corner. [Measured] Motion was not measured. [Inferred]
Themes
Light only. The dark color scheme pass changed nothing. [Measured]
Platform: iOS
How the FlixBus iOS app looks and behaves was not captured. FlixBus's component library is not documented in public, so every item below is inferred from the web design and platform conventions. No device capture was done.
Back and up navigation
Expected on iOS: Chevron plus previous title, swipe from the left edge.
Not measured. [Inferred]
Primary navigation
Expected on iOS: Bottom tab bar, about five items.
A bottom tab bar for search, trips and the account is expected. [Inferred]
Main action
Expected on iOS: Nav bar or bottom bar button.
A lime Search or Book button with dark text. [Inferred]
Sheets, dialogs and messages
Expected on iOS: Action sheets, alerts, modals.
Not measured. [Inferred]
Controls
Expected on iOS: Cupertino switches, pickers, segmented controls.
Not measured. [Inferred]
Text sizing
Expected on iOS: Dynamic Type.
Not measured. [Inferred]
Touch and pointer targets
Expected on iOS: 44pt minimum.
Not measured. [Inferred]
Insets and system bars
Expected on iOS: Safe areas, status bar.
Not measured. [Inferred]
Icons
Expected on iOS: SF Symbols or custom.
Not measured. [Inferred]
Account and sign-in rules
Expected on iOS: Equivalent login option when third-party sign-in exists (Guideline 4.8) and in-app account deletion. Note the date checked.
Not verified. Sign-in rules and account deletion were not checked. [Inferred] Checked: 2026-10-15 against the public web only.
Platform conformance
Expected on iOS: For each important component: what iOS expects, what this app does, and why it deviates.
The app is expected to share the lime, the dark gray text and the 6px corners with the web. [Inferred]
Platform: Android
How the FlixBus Android app looks and behaves was not captured. FlixBus's component library is not documented in public, so every item below is inferred from the web design and platform conventions. No device capture was done.
Back and up navigation
Expected on Android: System back and gesture, up arrow in the top bar.
Not measured. [Inferred]
Primary navigation
Expected on Android: Navigation bar, rail on tablets.
A bottom navigation bar for search, trips and the account is expected. [Inferred]
Main action
Expected on Android: Floating action button.
A lime Search or Book button with dark text. [Inferred]
Sheets, dialogs and messages
Expected on Android: Bottom sheets, dialogs, snackbars.
Not measured. [Inferred]
Controls
Expected on Android: Material switches, pickers, chips.
Not measured. [Inferred]
Text sizing
Expected on Android: Font scale.
Not measured. [Inferred]
Touch and pointer targets
Expected on Android: 48dp minimum.
Not measured. [Inferred]
Insets and system bars
Expected on Android: Edge to edge, system bars.
Not measured. [Inferred]
Icons
Expected on Android: Material Symbols or custom.
Not measured. [Inferred]
Account and sign-in rules
Expected on Android: Account deletion and data safety requirements. Note the date checked.
Not verified. Sign-in rules and account deletion were not checked. [Inferred] Checked: 2026-10-15 against the public web only.
Platform conformance
Expected on Android: For each important component: what Android expects, what this app does, and why it deviates.
The app is expected to share the lime, the dark gray text and the 6px corners with the web. [Inferred]
Platform: Web
The home page with its search bar, a city page and a not-found page, measured at 1440 and 390 wide.
Back and up navigation
Expected on Web: Browser back, breadcrumbs.
Browser back. [Observed]
Primary navigation
Expected on Web: Top nav or sidebar.
A 60 high lime header with Plan Your Journey, Service, Manage My Booking and Trip Tracker as 36 high items with a 6px corner, and a language menu. On mobile the items collapse and a small lime "Get the App" button sits in an app banner. [Measured]
Main action
Expected on Web: Page-level button.
A lime #97d700 Search button with dark gray 16px medium text and a 6px corner, 36 high on desktop and 44 on mobile, at the end of the search bar. [Measured]
Sheets, dialogs and messages
Expected on Web: Modals, toasts.
Not measured. [Inferred]
Controls
Expected on Web: Native or custom.
The search bar holds From and To fields, a Departure date button and a Passengers and Bikes button, each white with a 6px corner, 36 high on desktop and 42 to 44 on mobile. The bar itself is a white 84 high panel with a soft shadow. [Measured]
Text sizing
Expected on Web: Browser zoom.
Sizes are fixed pixel values that step down at the mobile width. [Measured]
Touch and pointer targets
Expected on Web: Pointer and keyboard.
Search fields and the button are 42 to 44 high on mobile and 36 on desktop. [Measured]
Insets and system bars
Expected on Web: Viewport, scrollbars.
Not measured. [Inferred]
Icons
Expected on Web: Any.
Icons sit in lime wash frames. [Measured]
Account and sign-in rules
Expected on Web: Not applicable unless the product has accounts.
Not checked on the pages measured. [Observed]
Platform conformance
Expected on Web: For each important component: what the web norm is, what this app does, and why it deviates.
A conventional booking site where the search bar stacks into full-width rows on mobile and grows to touch size. [Measured]
Cross-platform consistency
Consistent across platforms: the lime with dark text, Roboto and 6px corners. [Measured for web, Inferred for the apps]
Intentionally different: not measured. [Inferred]
Do's and Don'ts
Do
- Put dark gray
#353535text on lime, never white. - Use 6px corners for every control.
- Keep section headings small and bold (16 at 700).
- Use the pale lime wash for icon frames and selected tabs.
Don't
- Don't use black text. Use
#353535. - Don't round buttons into pills.
- Don't use lime for body links. Links are blue
#0047de.
Known Gaps
- Search results, seat choice, checkout and the account were not measured, and the help address returned a not-found page.
- The site redirected to its United States edition for the region we browse from, so other editions may differ.
- The iOS and Android apps were not captured, and FlixBus's component library is not documented in public, so every mobile topic is inferred.
- Motion and modals were not measured.
- The search band is a translucent blue. The hex here is that tint flattened on white.
- Account deletion and store policy rules were not verified.