Loading time too long :/

Comments

15 comments

  • Avatar
    Frank (Workflowy Support)

    Hi Johann,

    What sort of loading times are you and your friends getting on Android and elsewhere?

    0
    Comment actions Permalink
  • Avatar
    Johann

    Hi Frank,

    For my wife, on iOS, she is getting 10 seconds of loading time. My friends use the WebApp, and we're talking 15 seconds.

    0
    Comment actions Permalink
  • Avatar
    Frank (Workflowy Support)

    Hi Johann,

    So 10-15 seconds is pretty standard for now. It's expected. We're going to be working on solutions moving forward for faster loading. We're deliberating...

    1
    Comment actions Permalink
  • Avatar
    Johann

    I get your point, you got to set priorities and there are other matters to handle no doubt.

    Just letting you know, thanks for having considered :D

     

    0
    Comment actions Permalink
  • Avatar
    Frank (Workflowy Support)

    Hi Johann, 

    Loading speed is one of the most important things to us... it's just a tricky one to crack. It's the holy grail to us... and we're looking intently into it. In real time.

    0
    Comment actions Permalink
  • Avatar
    Johann

    Good luck with this tricky one :D

    0
    Comment actions Permalink
  • Avatar
    Jason

    I'll put in a vote for this as well. Loading takes ~7 seconds for me on iOS and ~26 seconds on macOS using Chrome. On iOS it's mostly frustrating because it reloads almost every time I switch to a different app and switch back. My day job is software development and I was a software tester in a previous life, so if I can provide more technical details to help debug or improve things I'm happy to help.

    0
    Comment actions Permalink
  • Avatar
    Johann

    I am upping this thread because things are getting worse :/. Right now, I have to wait for 45 to 60 seconds before being able to use the app, be it the Android app or the web app...

    1
    Comment actions Permalink
  • Avatar
    Jason

    Any updates on this? Any way we could get more details on approaches that are being considered? I've recently deleted tens of thousands of nodes to try to improve performance and it's still not great. More detailed information about the problem and solution space would make me feel a lot better about being able to use WorkFlowy in the long term.

    1
    Comment actions Permalink
  • Avatar
    Johann

    I must say I agree here :/

    0
    Comment actions Permalink
  • Avatar
    Henry Vanston

    Agree as well!

    I understand it loads all the bullets when starting up. How about loading all the bullets from the top level or two and then load the rest in the background? If a loaded bullet is clicked before everything is loaded, loading the sub-bullets real-time should be pretty quick.

    0
    Comment actions Permalink
  • Avatar
    Johann

    Yeah, I was thinking of a solution like that, but it does not work, because you need to be able to perform a search or an inline linking or mirroring from anywhere anytime, which only works if you have loaded the whole thing (especially when it comes to inline linking and mirroring).

    0
    Comment actions Permalink
  • Avatar
    Johann

    Or, you could go for a fast load, then background load with prioritisation of clicked bullet like Henry suggested, but with an indication that background loading it ongoing, so we know why some stuff are taking a bit longer to respond.

    0
    Comment actions Permalink
  • Avatar
    Daniel Nissenbaum

    I’d like to second this. WorkFlowy is my primary organizational app as a software developer and has been so for years. I have a very large WorkFlowy with an untold number of bullets. Loading on iOS has been slower and slower - typically minutes - but I don’t primarily use it on iOS so I’m willing to wait when I do need it on iOS and do something else while it loads. Problem is - starting recently - it just never completes loading, no matter how long I wait. It’s migrated from being an annoyance to a serious problem. I’d be happy to “flag bullets” as “not available on iOS” - including searching, tags, mirroring, etc - anything to make it possible for me to be able to get back to using the app on iOS. Thanks!

    1
    Comment actions Permalink
  • Avatar
    g.c.j. Bos

    For me the mobile app is unusable. Ive got a lot of nodes and screenshots, but that was the whole idea behind the app for me: a 2nd brain to store everything.
    I currently send myself an email and copy the content to the web version, which is far from cool.

    I have no clue about software development, but can WorkFlowy keep track of change date of a bullet? That would allow to download only the changed nodes since last load (the other ones are stored locally on the device). I understand it increases database size, but people seem to favor speed.

    In case it helps: happy to pay more for it

    1
    Comment actions Permalink

Please sign in to leave a comment.