The Pilots-Federation-Ingress
A framework for a ubiquitous and centralised suite of HTML based API-tools and modules, with design language resource for developer & player community communications.
The Current User cases which with the help of such a singular focused web-based solution will vastly improve the existing user experiences for all-round access, convenience and players immersive Role-playing experience as the game-design language and lore will be consistent across device/platform, giving the sensation of "player-presence" at every interface.
( cough a single solution cough * cough * sales/marketing *, devs will still have to frett between multiple versions, screens sizes, resolutions, and what info to allow to be open).
1) Client Launcher Container.
The client launcher is a pitiful little window with multiple panels that struggles with its own functionality, and any clicks open up the game or the default browser to complete the request since the shop, or videos are HTML based.
Having the launcher be a full-screen wrapper with a web-based interface could allow direct movement into the web-based training videos, the marketplace for game extras, player forums.
2) Game Client Container (overlay)
Announcements and community news/events are hidden from the game.
Training videos open a default browser to a video on the dangerous page or youtube.
Having a web-based overlay, again would keep the player-in-game, and keep the experiences consistent, especially if tied into the pilot's handbook/codex/journal.
3) Web Browser Container. (First-party or third-party)
The current web-page is a standard business model for selling the game and its extras.
It carries the design language of the game, but the aesthetics sit on top of the business-like-PR&sales-structured-navigation and web-interface (aka this is frontier-> these are the game we make -> here are the things that you can buy in the game -> here is some community stuff)
There are many player sites that try to combine a lot of the information for systems, markets, shipbuilding, engineers, tips and tricks and various entertaining content providers (art/videos) whereas others try to enhance the player experience with login/tools and having access to the player's journals.
Thus tailing the generic information to being more player orientated.
Which if Frontier were to craft web-modules for certain aspects of the game, as well as a design interface language (what colour is a title, what colour is a border and have that centralised so everything and anyone can use it (like the ships UI for example), allowing it to be altered).
The third-party pages could mix and match as some try to add information,
importing in a Dev-news module,
or Interstellar initiative module,
player-login module (giving access to unique f-dev player data).
4) Mobile Platform container. (First-party or third-party)
Similarly there a player based apps for general information or those that try to connect to the player's account.
Frontier did have the first-party app at launch, which the commander could see part of their current status.
Again the web-based interface (as with many mobile apps which have a device-specific wrapper which then has an in-app web-interface).
-----------------------------------------------------------------------------------------------------------------------------------------
My only hope is that the main-screen and forum revamp might be a step towards such a solution
A framework for a ubiquitous and centralised suite of HTML based API-tools and modules, with design language resource for developer & player community communications.
The Current User cases which with the help of such a singular focused web-based solution will vastly improve the existing user experiences for all-round access, convenience and players immersive Role-playing experience as the game-design language and lore will be consistent across device/platform, giving the sensation of "player-presence" at every interface.
( cough a single solution cough * cough * sales/marketing *, devs will still have to frett between multiple versions, screens sizes, resolutions, and what info to allow to be open).
1) Client Launcher Container.
The client launcher is a pitiful little window with multiple panels that struggles with its own functionality, and any clicks open up the game or the default browser to complete the request since the shop, or videos are HTML based.
Having the launcher be a full-screen wrapper with a web-based interface could allow direct movement into the web-based training videos, the marketplace for game extras, player forums.
2) Game Client Container (overlay)
Announcements and community news/events are hidden from the game.
Training videos open a default browser to a video on the dangerous page or youtube.
Having a web-based overlay, again would keep the player-in-game, and keep the experiences consistent, especially if tied into the pilot's handbook/codex/journal.
3) Web Browser Container. (First-party or third-party)
The current web-page is a standard business model for selling the game and its extras.
It carries the design language of the game, but the aesthetics sit on top of the business-like-PR&sales-structured-navigation and web-interface (aka this is frontier-> these are the game we make -> here are the things that you can buy in the game -> here is some community stuff)
There are many player sites that try to combine a lot of the information for systems, markets, shipbuilding, engineers, tips and tricks and various entertaining content providers (art/videos) whereas others try to enhance the player experience with login/tools and having access to the player's journals.
Thus tailing the generic information to being more player orientated.
Which if Frontier were to craft web-modules for certain aspects of the game, as well as a design interface language (what colour is a title, what colour is a border and have that centralised so everything and anyone can use it (like the ships UI for example), allowing it to be altered).
The third-party pages could mix and match as some try to add information,
importing in a Dev-news module,
or Interstellar initiative module,
player-login module (giving access to unique f-dev player data).
4) Mobile Platform container. (First-party or third-party)
Similarly there a player based apps for general information or those that try to connect to the player's account.
Frontier did have the first-party app at launch, which the commander could see part of their current status.
Again the web-based interface (as with many mobile apps which have a device-specific wrapper which then has an in-app web-interface).
-----------------------------------------------------------------------------------------------------------------------------------------
My only hope is that the main-screen and forum revamp might be a step towards such a solution