📝 Context:

ORIGINAL POST

Hi everyone,

I'm working on a Flutter app that takes a bit too long to launch and navigate to the home screen. I would really appreciate some advice on how to improve performance, especially during startup.

📝 Context:

During the app launch, several steps are executed before reaching the home screen:
- Initialization of Firebase and other external services.
- Setting up authentication with user verification (tokens, verification status, etc.).
- Checking local preferences for user session management.
- Fetching data from an API to initialize some blocs and states.
- Loading dependencies via blocs and cubits in the main() function.
Once services are ready, the app uses a navigation handler to manage redirection based on the user’s connection status.
After initialization, the app goes through a wrapper screen to ensure everything is properly set up before navigating to the home screen.

🚦 Problem:

Despite optimizing some steps, there is still a noticeable delay between launching the app and displaying the home screen. I tried deferring some API calls, but it didn't make much difference.

❓ Question:

What are some best practices to reduce loading time during the initialization of a Flutter app, especially when using blocs/cubits and backend services like Firebase? Any tips on improving smoothness during redirection and managing navigation after launch?

Thanks in advance for your suggestions!

8 replies

NoExample9903 · 5 months ago

How long does it take? And is it also slow in prod? The app I work on is quite large and does lots of stuff on launch. from pressing the icon until its ready for use is 1-3 seconds, sometimes slower if its an old device. I’ve never had bad feedback because of launch time

2 upvotes on reddit

or9ob · 5 months ago

Similar. My app has 7 steps at startup (very similar to what OP is describing, with Firebase init, Version check, Feature toggle service checks, initializing a few hard dependencies) and it takes less than 300-500ms on most devices (we track it with Firebase Performance).

1 upvotes on reddit

These-Mycologist7966 · OP · 5 months ago

The app typically takes around 3-4 seconds to launch in production. While this is generally acceptable and we haven't received negative feedback regarding the launch time, I believe there's room for improvement. I'm actively looking into ways to optimize the startup process to make it even faster.

1 upvotes on reddit

NoExample9903 · 5 months ago

If you’re making lots of api calls in a row, wrap them in a future.wait to make the calls simultaneously. If you’re fetching data that isn’t required straight away then fetch it after the app is running

1 upvotes on reddit

Markaleth · 5 months ago

The simplest "quick wins" i can suggest are:

do lazy loading of BLOC components. No point in creating instances of objects you might not need.
use cached data vs fetching new data each time the app is started up (where possible)
have some sort of session management mechanism that doesn't require you to check with the server on startup each time (firebase should already have this covered, but for a custom BE, you could, for instance, just persist your auth cookies and clear them on sign out). You mentioned you have this already. If that's the case, why do you need to call the BE to confirm the user is logged in?
why do you need to "check everything is set up"? I don't understand why you have this step in your initialisation process. Do you like, check if user != Null and stuff? Maybe you can drop this step altogether.

You can probably do some more advaned stuff like background fetches or moving some of your requests or initial setup to isolates where (and if) that makes sense for your use case.

The general rules of thumb here are:

lazy load as much as possible
use caching

That being said, a few notes to keep in mind are:

1st app starts are always slower because of shader warmup and cache generation
you can get a good sense of your app performance with Firebase Performance. 1-3 second start times are HUGE. You should be under 1 sec till "1st frame rendered" most of the time regardless of user network conditions (after 1st app start that is).

Hope it helps!

1 upvotes on reddit

These-Mycologist7966 · OP · 5 months ago

I've looked into your suggestions and they make a lot of sense. Here's what I plan to do:

Lazy loading of BLOCs: I'll make sure not to initialize all the BLOCs at app startup, only when needed.
Using cached data: Instead of making API calls on every launch, I'll load from local storage first (e.g., SharedPreferences) and update data in the background.
Reducing server checks: Since Firebase handles session management well, I'll avoid redundant checks if the user is already logged in.
Splitting initialization into phases: I'll display a lightweight splash screen quickly and perform heavier tasks (like user data validation) asynchronously in the background.
Isolates for heavy tasks: I'll move some blocking operations to isolates, especially when fetching large datasets.

Also, I realized that some of the loading delay might be due to the debug mode itself, as it doesn't fully represent the production environment. I'll run performance profiling in production mode to get a better picture.

Thanks again for the great advice!

1 upvotes on reddit

chrabeusz · 5 months ago

If you are awaiting for multiple things in startup, make sure you are using Future.wait instead of serially awaiting one at a time.

1 upvotes on reddit

Comment-Mercenary · 5 months ago

It's hard to say what's wrong without seeing the code, but everything that loads at the beginning needs to be loaded at that time?

1 upvotes on reddit

See 8 replies

r/immich • [2]

Summarize

bad performance in iOS and android apps

Posted by msh404 · in r/immich · 3 months ago

Are there any optimization guides or performance help with the immich app for iOS and android? I have a iphone 15 and a galaxy s23 and in the app there is constant stuttering and freezing. On android it often pops up that the app is unresponsive and asks me if I want to wait or kill the app.

If I access the library web interface from a different computer than the one hosing immich the performance is perfect without issue, its only the apps.

- I am running the docker image of immich on my m1 mac mini.

- I have a library of approximately 74000 photos and videos.

The phones are connected with wifi to the same network as the mac mini.

I have tried turning on the "prefer remote images" setting but it seems not to make a difference.

6 upvotes on reddit

11 replies

Helpful

Not helpful

11 replies

Paul_Vangreen · 3 months ago

Same here. App is written in flutter. I write some apps in this framwework and I know people who write flutter apps for living. These applications will not have the same performance as those written natively. And it’s really hard to make it perform smoothly. Even simple apps struggle with it. I believe it’s easier for Immich team to write one code for all three platforms (iOS, android, web), but unfortunately it is at the cost of performance.

2 upvotes on reddit

altran1502 · 3 months ago

The problem is with the sync mechanism running on the UI thread, we are working on moving them to the background and it’s pretty promising so far

4 upvotes on reddit

YoxtMusic · 3 months ago

I totally agree, I made apps in flutter and even simple apps felt sluggish on iOS. When I made the same app in native it was 10 times faster.

1 upvotes on reddit

PerfectReflection155 · 3 months ago

I run the iOS app and like many was having performance issues. No one mentioned to try enabling the option to prefer remote images under advanced setting.

Simply enabling that option resolved the iOS performance issues for me. It’s now super fast no issues

4 upvotes on reddit

ResponsibleRevenue63 · 3 months ago

Great! What’s its cons?

1 upvotes on reddit

PerfectReflection155 · 3 months ago

Personally I have not found any cons. If I think of 1 perhaps it would be that you would use more internet data when outside of home accessing photos.

I have a powerful server running Immich so that also contributes possibly to no cons found to this setup.

Gigabit internet for external connection

Striped 2x SSDs for storage of photos

i5 8400 CPU running docker container

1 upvotes on reddit

Grdosjek · 3 months ago

It works slow while app is creating timeline. Once it's finished it'w working good. I think devs said that it's being worked on, that they are moving timeline building and other similar workload out of main thread so once it's done it should work good no matter how large pic library is.

1 upvotes on reddit

moebiusss · 3 months ago

Give a try also to logout/login back, that greatly improved the issue for me.

1 upvotes on reddit

altran1502 · 3 months ago

The issue is with the sync mechanism happens on the main thread, causing the UI to be janky. We are reworking this mechanism, the progress is very promising in making the app really smooth regardless of library size

14 upvotes on reddit

ResponsibleRevenue63 · 3 months ago

Amazing, thanks! When can we see it roll out?

1 upvotes on reddit

altran1502 · 3 months ago

Hopefully within the next two months

5 upvotes on reddit

See 11 replies

r/homeassistant • [3]

Summarize

iOS App - reduce app load times

Posted by matt827474 · in r/homeassistant · 4 years ago

The iOS app is amazing, so thanks to the developers for all the hard work.

I’m wondering if there’s a way to reduce load times by background syncing the dashboards or using web sockets to only refresh changes without having to load the whole dashboard?

It takes about 3 seconds to load, which isn’t a major issue, just really annoying when you want to do something fast like turn on a light.

Edit: the delay is a home assistant splash screen with a loading icon saying “loading data”. I’m using Nabu Casa too, but testing this while on wifi on my local network. Loading home assistant on my web browser is instant.

10 upvotes on reddit

8 replies

Helpful

Not helpful

8 replies

ams123r · 4 years ago

How long does it take to load in a browser on your phone? I have found you don't want to have history graphs on your main page if load time is important.

2 upvotes on reddit

matt827474 · OP · 4 years ago

It loads instantly on a web browser on the same device.

1 upvotes on reddit

JATD2020 · 4 years ago

My app opens the dashboard within one second after I force close it. I don’t have any history graphs on first page but lots of conditionals

2 upvotes on reddit

Reallytalldude · 4 years ago

Are you on wifi or 4g?

When I’m on wifi it’s super fast, but when I switch to 4g it takes a couple of seconds.

Are you using nabu casa? I like it, but I did find it a bit slower than a direct connection - likely as it needs to go through some servers far away from me which adds some latency.

2 upvotes on reddit

matt827474 · OP · 4 years ago

I’m on wifi. I use Nabu Casa, but I thought that when you’re on the local network it bypasses that and goes straight to the local server?

The delay is a home assistant splash screen with a loading icon and the text “loading data”.

1 upvotes on reddit

Reallytalldude · 4 years ago

Yep, locally it bypasses nabu casa. My first screen is mostly buttons , no graphs or other. Maybe that’s why it loads faster? Maybe create an additional first page in Lovelace with the key buttons you need so that you have quick access?

1 upvotes on reddit

matt827474 · OP · 4 years ago

I think I found the issue. It didn’t have local URL in the app config. Strange, because before the Nabu Casa setup used to automatically handle this. It’s much faster now! Thanks everyone.

2 upvotes on reddit

pheellprice · 4 years ago

It takes me less than a second and my dashboard is a mess.

2 upvotes on reddit

See 8 replies

r/androiddev • [4]

Summarize

Reduce Your Android App Startup Time by 30% with This Simple Change!

Posted by Entire-Tutor-2484 · in r/androiddev · 3 months ago

I recently ran into a startup lag issue in one of my native Android apps (written in Kotlin). After profiling with Android Studio Profiler, I realized initializing some heavy SDKs inside Application.onCreate() was the culprit.

Here’s what I did:

Moved non-critical SDK initializations to a background thread using WorkManager.
Deferred some lazy object creations until actually needed.

This makes startup time dropped from 1200ms to 800ms on a mid-range device.

Tips

Keep your Application.onCreate() as light as possible.
Profile startup with Android Profiler → System Trace.

i.redd.it

52 upvotes on reddit

12 replies

Helpful

Not helpful

https://github.com/raghavsatyadev/SimpleCricketUmpireScorer

12 replies

KobeWanKanobe · 3 months ago

Android profiler kept crashing my app. Unsure why that was though.

6 upvotes on reddit

Entire-Tutor-2484 · OP · 3 months ago

yeah profiler can be super unstable sometimes… i noticed it struggles a lot with big apps or when you have too many background threads spawning at once on cold start. you on a physical device or emulator when it happened?

1 upvotes on reddit

Lost_Fox__ · 3 months ago

Why would you use WorkManager to initialize something in a background thread?

6 upvotes on reddit

Entire-Tutor-2484 · OP · 3 months ago

yeah fair question… in my case a couple of SDKs needed to do stuff even if the app gets killed n reopened later… like crash reporting or analytics uploads… so WorkManager made sense for those… for regular inits yeah Dispatchers.Default would totally work

1 upvotes on reddit

No-Instruction9159 · 3 months ago

You can also use app startup API for SDK initialization https://developer.android.com/topic/libraries/app-startup

16 upvotes on reddit

RJ_Satyadev · 3 months ago

I am using them heavily in my new project, although it is still incomplete, you can check it out here, I am currently moving the XML code to Compose as I recently learned it.

Using Hilt + Compose + StartUp libraries in this one.

4 upvotes on reddit

Entire-Tutor-2484 · OP · 3 months ago

yeah true… App Startup API’s neat for stuff like this too… have u tried comparing it with WorkManager for cold start cases? curious if there’s any noticeable diff 👀

1 upvotes on reddit

sevbanthebuyer · 3 months ago

Why did you need WorkManager ? Why not a simple background context like Dispatchers.Default or IO ?

27 upvotes on reddit

Entire-Tutor-2484 · OP · 3 months ago

yeah for one-time inits during startup Dispatchers.Default works fine… in my case some of em needed to persist or retry if the app restarted so WorkManager felt safer… but def depends on the usecase

5 upvotes on reddit

Lost_Fox__ · 3 months ago

I think WorkManager is way less consistent. It can delay running something for a long time. It just adds way more layers and difficulty to actually running something.

It's hard for me to imagine a scenario where WorkManager is correct to use. It would have to take many seconds to initialize to even begin thinking about that being the correct option.

13 upvotes on reddit

TypeScrupterB · 3 months ago

Dont forget about the null pointer crashes

3 upvotes on reddit

Entire-Tutor-2484 · OP · 3 months ago

haha yep… no matter how modern the SDK gets, null’s always lurking in the shadows 👻

0 upvotes on reddit

See 12 replies

r/AndroidStudio • [5]

Summarize

5 Android performance tips every dev should know based on real-world pain

Posted by Moresh_Morya · in r/AndroidStudio · 2 months ago

Android devs performance tips that saved my apps (and sanity):

Shrink your APK early – Use R8/ProGuard, remove unused assets, and split ABIs. Smaller APK = faster installs.
Don’t block the main thread – Keep network calls, JSON parsing, etc., in coroutines or WorkManager. Blocking UI = ANRs.
Handle images wisely – Resize bitmaps (inJustDecodeBounds) and use Glide/Picasso/Fresco. Saves memory, smooths UI.
Flatten layouts – Ditch deep nesting. Use ConstraintLayout for better rendering speed.
Profile on real devices – Emulators lie. Test on low-end phones. Watch CPU, memory, overdraw, and image load time.

These lessons came from painful debugging sessions. Got any favorite performance tricks or tools? Let’s swap ideas!

8 upvotes on reddit

2 replies

Helpful

Not helpful

2 replies

FrezoreR · 2 months ago

Flatten layouts sure. However, CL is not a silver bullet. It can be pretty expensive comparatively.

1 upvotes on reddit

h_bhardwaj24 · 2 months ago

network calls, JSON parsing in Work Manager?

1 upvotes on reddit

See 2 replies

r/FlutterDev • [6]

Summarize

Is upgrading to Flutter 3.35 worth for performance?

Posted by Wefaq04 · in r/FlutterDev · 14 days ago

My app do heavy JSON reading on multi-threads, at startup it lags on slow phones, I read latest Flutter release have improved the engine performance, will that improve my app performance?
the app startup time 3 seconds on decent phones but on slow phones can take 5-6

28 upvotes on reddit

11 replies

Helpful

Not helpful

11 replies

tommytucker7182 · 14 days ago

Sounds more like a caching problem than a UI problem.

Need to try cache OR preload the bare minimum data to start the app.

then once that's done, Need to use all the tricks in the book to make the app look quick even when it's working on something.

Also you don't say what version you are on now? If it's a relatively old one then you will pickup some perf improvements, but I think engine performance isnt the problem here.

8 upvotes on reddit

Wefaq04 · OP · 14 days ago

I work on Flutter 3.24, I do cache to be able to run isolates without rootBundle

2 upvotes on reddit

chrabeusz · 14 days ago

For your use case: probably not.

You may improve this a lot by replacing json with a prefilled sqlite database or maybe protobuf.

36 upvotes on reddit

Wefaq04 · OP · 14 days ago

Will try but does SQLite result in bigger file size? The total json files 200mb but with apk compression become 15mb, does that happen same for sqlite?

4 upvotes on reddit

eibaan · 14 days ago

If 200 MB can be compressed by factor 13 to 15 MB, your JSON doesn't contain much information (according to information theory). You might want to preprocess the data before adding it to your application.

Some kind of custom binary encoding might be faster to parse. However, keep in mind that Dart uses a highly optimized JSON parser as part of the runtime which might process data faster than your own code written in Dart, especially if you're not careful with allocations.

Still, if you parse JSON into some kind of class instances (instead of using the raw Map, List and String values) I'd attempt to directly deserialize your data into those instances.

Or even better, don't load the data at all. Do you need every byte of that JSON file in memory all the time? Using an sqlite3 file might allow index-sequential access. However, that index will need additional space, so the file might not compress as well as your JSON.

Again, a custom file format might come handy. If your JSON is basically a set of data records, you might want to read in an index that tells you where to seek in a RandomAcessFile object for the single record you need. Switch from JSON to JSONL, then you can still read an individual object like before.

33 upvotes on reddit

chrabeusz · 14 days ago

Good question. No idea. sqlite file will be likely smaller but may not compress as well.

5 upvotes on reddit

alexmercerIND · 14 days ago

200 mb json is no joke

3 upvotes on reddit

battlepi · 14 days ago

Compression happens. The db by default will store it far more efficiently, then it will compress.

1 upvotes on reddit

eibaan · 14 days ago

Random people on the internet won't help you with vaguely formulated performance questions. Run your app (or if you have too many shady dependencies that doesn't work anymore with the current version of Flutter create a demo) and measure the performance.

For a json.decode call, you don't even need a Flutter app. A simple AOT compiled Dart program is sufficient.

Hopefully you already measured that this call is the culprit and not some other part of your application.

18 upvotes on reddit

padetn · 14 days ago

Flutter engine is going to mean UI performance, JSON parsing is a Dart thing.

31 upvotes on reddit

No-Echo-8927 · 14 days ago

I've not seen much speed improvements by updating to the latest. I did however have to deal with a gradle update that lost me 2+ hours of my time

4 upvotes on reddit

See 11 replies

r/Nest • [7]

Summarize

How to speed up app load time?

Posted by lets_go_fire · in r/Nest · 5 years ago

I have many Nest devices and it takes about 10-15 seconds to load the app on my iPhone.

Does anyone have suggestions for how to speed this up?

Thank you.

2 upvotes on reddit

6 replies

Helpful

Not helpful

6 replies

Somar2230 · 5 years ago

It loads in 5 to 7 seconds for me on an iPhone Xs Max and the same on a Pixel 2 XL on WiFi.

6 to 8 seconds on both phones on LTE.

I only have a few devices though and have Spaces set to off.

2 upvotes on reddit

mckstpat · 5 years ago

I have an iPhone 11 and it takes 3-5 seconds to load until I see a camera feed. I do not have nest secure. Do the people experiencing longer load times have nest secure?

1 upvotes on reddit

millarrp · 5 years ago

I have my doubts it will improve. I’m under the impression they are rolling all of the nest app features into the google home app so I wouldn’t be surprised that is where their effort is going.

1 upvotes on reddit

DrkMith · 5 years ago

Use an android phone instead ��....sorry......couldn't help myself

6 upvotes on reddit

lets_go_fire · OP · 5 years ago

Yes...but aside from that option...any other suggestions?

2 upvotes on reddit

TricksyPrime · 5 years ago

Just tested my app load time (iPhone 11 Pro) and yeah it’s about 12 seconds. We even have pretty fast WiFi (250Mbps). Not sure if there’s much else we can do : (

3 upvotes on reddit

See 6 replies

r/FFRecordKeeper • [8]

Summarize

Does anyone have any good tips on reducing load times?

Posted by Blauwal · in r/FFRecordKeeper · 7 years ago

I love FFRK, but the load screens are so much more obtrusive than other mobile games I've played lately, and it's really frustrating how often and how slowly navigating the game can be. I currently have a Samsung Galaxy S8, which I set to "Game mode" to improve performance. Is there anything I can change in my settings? I've seem Game Booster apps before as well, are there any good ones? I'm always worried that they might not do anything but spam me with ads.

8 upvotes on reddit

5 replies

Helpful

Not helpful

5 replies

sonicandfffan · 7 years ago

Don't play as often

Less game time = less load time

#shittylifehacks

1 upvotes on reddit

Blauwal · OP · 7 years ago

Thanks for the tips. I'll see if I can trim down my storage, or go back to emulating. I prefer using my phone, but I guess I'll just have to cope.

1 upvotes on reddit

ZeroEdgeir · 7 years ago

It's the game itself. Not much can be done. Not even emulator or a different phone will resolve it in any meaningful way (I play on my phone, a Sony Xperia XA1 Ultra, and Nox Emulator, no real difference).

It is what it is, just have to accept it.

3 upvotes on reddit

thedaveness · 7 years ago

Make sure you’re not close to the limit on phone storage. Constantly download your photos and clear em out as well as all the duplicate photos in texts to people.

2 upvotes on reddit

Zak8022 · 7 years ago

As an iPhone user, I’m sorry. People say load time is better on iPhones, but I don’t have an android anymore to test. Well, I have Nox, but that loads just as fast if not faster than my iPhone 7.

I’d be curious to see some side by side video of it... not that it would really solve anything.

1 upvotes on reddit

See 5 replies

r/Angular2 • [9]

Summarize

Improving load times on angular applications

Posted by cristianflorincalina · in r/Angular2 · 3 years ago

Hello !

I'm new here, but I wanted to share with you this article that I wrote regarding performance optimizations for initial load times for angular applications. It might not be for everybody, but I wanted to share with you some of the steps I took in order to improve the TTI for an enterprise angular application.

Let me know what you think and if you like it, hit that Clap button and follow me because I am planning to write more and more.

6 upvotes on reddit

1 replies

Helpful

Not helpful

1 replies

Lazy_Cash_744 · 3 years ago

If your application is considerably large with multiple complex components in the first screen, you can try to lazy load such components with custom loading logic. You can prioritize critical components and then move on to rest. But fair warning this will make the application complicated.

2 upvotes on reddit

See 1 replies

r/AppStoreOptimization • [10]

Summarize

How important is the first app release?

Posted by kaizenrkgd · in r/AppStoreOptimization · 19 days ago

I’m about to launch my first ever app and for the first time on the App Store but there are some optimisations I want to make after. Should I be worried about launching it prematurely or will I be fine after? I’ve seen people say there’s a boost when you first launch your app but I’m not sure how true that is

8 upvotes on reddit

11 replies

Helpful

Not helpful

11 replies

AppLaunchpad_ · 19 days ago

Launching your app prematurely can be a double edged sword…..yes the App Store gives new releases a short term boost, which can help you gain initial downloads and user feedback. However, this advantage will fade quickly if your app lacks polish

1 upvotes on reddit

DabbosTreeworth · 19 days ago

Just ship the MVP. Don’t rely on new app ‘boost’, many people in the space agree this doesn’t happen on the App Store after algorithm changes, and I have never noticed it at all on Android. Your app will have bugs. Test it daily from as many devices as possible. Get feedback, tune keywords, rinse and repeat. Add/remove features based on feedback and testing. The days of building a perfect app and then shipping with fanfare are long over. Ship fast and test in production, or fall behind

3 upvotes on reddit

entercoffee · 18 days ago

Regarding the first-release boost, I can confirm that it’s no longer there. I have several apps in a App Store that are fairly similar in functionality (digital versions of old encyclopedia), and there was no noticeable boost in the last app I released (around May 2025).

2 upvotes on reddit

AcesUp3D · 17 days ago

Yep and apps get rejected even more often for any little thing, Apple’s way of cutting down AI slop in their store. Meanwhile, Android is still so easy and painless; except the unfortunate play console ui update

1 upvotes on reddit

salamat36 · 19 days ago

It's true most of the time apps get initial boost and yeah to maintain that boost you have to meet the required KPIs.

2 upvotes on reddit

Tom42-59 · 19 days ago

What are the required KPIs?

1 upvotes on reddit

salamat36 · 18 days ago

Here are some of them.

CR
D1R
D7R
ARR
CFS
MAU
F2P CR
UR
SL
DAU/MAU

2 upvotes on reddit

Joggle-game · 19 days ago

In my experience, the first release must be bug-free and have all the core functionality, UI/UX etc. in place. Bells and whistles can come later. There is a short term (1-2 weeks) boost initially, but if you launch it half-baked and get a few low ratings/reviews, your downloads and visibility will suffer despite subsequent polishing / bug-fixing.

4 upvotes on reddit

kaizenrkgd · OP · 19 days ago

Thank you for this - I’ll test my app thoroughly to make sure there are no bugs remaining!!

1 upvotes on reddit

Otherwise9477 · 19 days ago

Just make sure you maintain user data transparency and adhere by content safety policy to not get rejected.

Keep options like report a profile if somethings fishy, or let the users know why you are accessing there gallery as clear as possible.

2 upvotes on reddit

kaizenrkgd · OP · 19 days ago

Ahh thank you for this reminder!! I need to also update my terms of use

2 upvotes on reddit

See 11 replies

Top People to Talk to

These are some of the top contributors related to

FlutterDev

immich

homeassistant

5+ others

NoExample9903

No bio available

157

Karma

Posts

213

Comments

altran1502

No bio available

13571

Karma

135

Posts

3605

Comments

Reallytalldude

No bio available

20860

Karma

Posts

5439

Comments

chrabeusz

No bio available

8136

Karma

Posts

2022

Comments

ams123r

No bio available

556

Karma

Posts

324

Comments

JATD2020

No bio available

692

Karma

Posts

101

Comments

pheellprice

No bio available

8389

Karma

Posts

826

Comments

eibaan

No bio available

4160

Karma

192

Posts

4824

Comments