Back

Announcements & News

The latest announcements and Flight Rising news.
TOPIC | Dev Update: 2022 Goals
[center][permalink][img]https://flightrising.com/dropbox/updates/devupdate.png[/img][/permalink][/center] [center]We wanted to provide a quick update to our [b]development goals for 2022[/b]. [permalink][b]Click here to read the update.[/b][/permalink][/center] [more] -------- Hello, [i]Flight Rising[/i] community! We're in the final development stages for some really fun stuff (Arlo's Ancient Artifacts, our next Ancient Breed, and more) and can't wait to get those out to you. We also wanted to provide you with [b]a brief update about some development goals we're hoping to achieve in 2022, because we're taking a slightly different approach[/b]. [size=5][b]Refactors VS Revamps (For Now)[/b][/size] As many of you know, [i]Flight Rising[/i] has been [b]undergoing a code refactor for many years now[/b]. Our engineering team has not only been working hard to deliver new features for the game, but also [i]completely rewrite[/i] older ones, revamping them in the process (combining popular QOL suggestions from the community and new functional and visual bells and whistles that our team has always wanted to add). However, for as long as the refactor project has been in progress, it has put the site and our team at somewhat of a disadvantage. [i]Flight Rising[/i] is spread across two subdomains and two codebases, which creates a significant amount of extra work and testing every time we want to add a new feature or fix. [b]For example[/b]: If part of a feature revamp touches multiple pages and systems, we very well might need to [b]write code for it two times in two different ways[/b], which drags out not only the development of that revamp, but everything else after it. We also have to [b]write and execute two unique sets of testing[/b], because having redundant code opens us up to more risk for bugs in one or more versions of it. Internally, having a split codebase also causes logjams for other vital infrastructure work, and can impede [i]Flight Rising[/i] from being recognized in the most optimal way in Google searches, etc. With that in mind, [b]we have made the choice as a team to place revamps on a brief hold and refactor the remaining features as they operate now (i.e. "one to one"), without placing too much time on adding functional improvements to them[/b]. Doing straight ports of the remaining features allows us to clean them off our plate far quicker, leading us to wrap up the site refactor sooner, which ultimately enables us to move into working solely on new stuff, which is the most rewarding work for us and for you. [b]We want to be clear: this does not mean we are ending work on revamping old features[/b], and there may be one or two that still get revamped while they are being refactored (depending on their complexity). We are simply hastening to bring a very long project to a swifter end so that we can move forward with new features and revamps alike. Because these feature revamps are going to be simply conversions, there likely will be less fanfare surrounding them, but we'll do our best to communicate timetables, and when and if we need some maintenance to deploy them, so that you are prepared. 2022 is going to be a good realignment year for our team, and we're excited to hopefully put a very long, resource-heavy project behind us so that we can really begin on the really fun stuff ahead of us. [emoji=obelisk happy size=1] ------- EDIT: We've been getting a few questions asking for a little more clarity on just [b]what we're focusing on[/b]. While I can't give you major specifics (the nature of project management changes literally day-to-day and hour-to-hour), here are a few of the things that we're hoping to refactor this year, if we can fit them all in alongside new content and new features: [LIST] [*]The Dominance standings page [*]Gathering & Gathering Results [*]Clan Profile [*]Nesting Grounds [/LIST] This list is not all-encompassing, but gives you a glimpse of what we currently think is manageable at this moment in time. We could shorten or add to this list as we continue to meet and evaluate progress.
devupdate.png
We wanted to provide a quick update to our development goals for 2022.

Click here to read the update.



Hello, Flight Rising community!

We're in the final development stages for some really fun stuff (Arlo's Ancient Artifacts, our next Ancient Breed, and more) and can't wait to get those out to you. We also wanted to provide you with a brief update about some development goals we're hoping to achieve in 2022, because we're taking a slightly different approach.

Refactors VS Revamps (For Now)

As many of you know, Flight Rising has been undergoing a code refactor for many years now. Our engineering team has not only been working hard to deliver new features for the game, but also completely rewrite older ones, revamping them in the process (combining popular QOL suggestions from the community and new functional and visual bells and whistles that our team has always wanted to add).

However, for as long as the refactor project has been in progress, it has put the site and our team at somewhat of a disadvantage. Flight Rising is spread across two subdomains and two codebases, which creates a significant amount of extra work and testing every time we want to add a new feature or fix.

For example: If part of a feature revamp touches multiple pages and systems, we very well might need to write code for it two times in two different ways, which drags out not only the development of that revamp, but everything else after it. We also have to write and execute two unique sets of testing, because having redundant code opens us up to more risk for bugs in one or more versions of it.

Internally, having a split codebase also causes logjams for other vital infrastructure work, and can impede Flight Rising from being recognized in the most optimal way in Google searches, etc.

With that in mind, we have made the choice as a team to place revamps on a brief hold and refactor the remaining features as they operate now (i.e. "one to one"), without placing too much time on adding functional improvements to them. Doing straight ports of the remaining features allows us to clean them off our plate far quicker, leading us to wrap up the site refactor sooner, which ultimately enables us to move into working solely on new stuff, which is the most rewarding work for us and for you.

We want to be clear: this does not mean we are ending work on revamping old features, and there may be one or two that still get revamped while they are being refactored (depending on their complexity). We are simply hastening to bring a very long project to a swifter end so that we can move forward with new features and revamps alike.

Because these feature revamps are going to be simply conversions, there likely will be less fanfare surrounding them, but we'll do our best to communicate timetables, and when and if we need some maintenance to deploy them, so that you are prepared.

2022 is going to be a good realignment year for our team, and we're excited to hopefully put a very long, resource-heavy project behind us so that we can really begin on the really fun stuff ahead of us.


EDIT: We've been getting a few questions asking for a little more clarity on just what we're focusing on. While I can't give you major specifics (the nature of project management changes literally day-to-day and hour-to-hour), here are a few of the things that we're hoping to refactor this year, if we can fit them all in alongside new content and new features:
  • The Dominance standings page
  • Gathering & Gathering Results
  • Clan Profile
  • Nesting Grounds
This list is not all-encompassing, but gives you a glimpse of what we currently think is manageable at this moment in time. We could shorten or add to this list as we continue to meet and evaluate progress.
Flight Rising Developer
Project Management | Engineering Team Cheerleader | UI Designer
Hello all! Please remember to stay on topic. If you have any suggestions for features, please be sure to post them in the Suggestions Forum. Thank you!
Hello all! Please remember to stay on topic. If you have any suggestions for features, please be sure to post them in the Suggestions Forum. Thank you!
Woot, woot!

But no, that makes perfect sense.
Woot, woot!

But no, that makes perfect sense.
Watercolor Commissions!
The Seasonal Courts
Watermelons Unite!
Starborn Prophets
Nuvole Bianche
Oilbelisks
7b6489c2d3258498730fa4bcacfe6b51b29044f7.png
Exciting! I cannot wait to see what you guys have planned. :)
Exciting! I cannot wait to see what you guys have planned. :)
WOAH NICE oh that is awesome and completely understandable. Doing refactors first makes total sense, it gets you a nice template to work on, I see why and how that'll move things faster! Good luck and excellent work so far, can't wait to see the upcoming stuff [quote name="Xhaztol" date="2022-01-10 13:00:10" ] so that we can really begin on the really fun stuff ahead of us. [emoji=obelisk happy size=1] [/quote] I smell Adventure Mode [emoji=normal eyes size=1] let's get things out of the way so we can get that fun stuff >:^)
WOAH NICE

oh that is awesome and completely understandable. Doing refactors first makes total sense, it gets you a nice template to work on, I see why and how that'll move things faster! Good luck and excellent work so far, can't wait to see the upcoming stuff
Xhaztol wrote on 2022-01-10 13:00:10:
so that we can really begin on the really fun stuff ahead of us.

I smell Adventure Mode let's get things out of the way so we can get that fun stuff >:^)
Link to art shopLink to skin shopImage depicting a large blue crab carrying produce on their back, its purpose being a background element for the signatureLink to a personal log thread containing various different links, information and sources
horaaay!!!
horaaay!!!
act
imp inthusiast
he/him
please ping on reply
Wq7yxTc.gif
exchange
Nearku%2527s%2BDya.png
hatchbannersmall.png
Nice
Nice
ew9u8Xp.png
Woo!
Woo!
Check out my 3D art shop!
Help me fill my Antiquary!

My Wishlist!
Sounds good!
Sounds good!
vlHpjp8.png .
he/him

FR+3:00
. .
checked on swipp, baldwin, or arlo lately?
_ wizardry2.gif
o hello
o hello
s9K2ty1.pngCompl-1.pngyNBFlay.png HL3uioH.png
tyEuRXe.png
nIu3Z9d.png
mlHpBMC.png
swampshine1.gif
button credit