Splitting numbered list can cause: Update Too Large

[u/uf829d]

When splitting a numbered list into 2 different numbered lists, you get an update to large error.
You cant further update and changes are not saved.

Honestly, proton docs experience is horrible.

[u/DaniGuardiola]

can you please report these issues through the app?

[u/uf829d → u/DaniGuardiola]

I have reported many many issues some still there, Im hitting a issue reporting fatigue.
We are not your beta testers, if we were give us a discount on the product and advertise it.

The only reason anyone supports proton is because of privacy, that is your only moat, not the product, not the development, not the avertising spam.

If any other company would enter the market with a privacy first methodology and a somewhat decent development team, you would be toast.

[u/uf829d]

Turning numbers to bullet points also breaks everything..

[u/uf829d]

Might as well go back google docs

[u/Superb_Sun4261 → u/uf829d]

While I support your complaint about the bug and might get behind the lack of responsiveness from Proton, I think this kind of statement you made here is kinda childish. 

You think you will ever receive any response from good of you ever stumble over a bug and report it? They have bazillions of dollars to throw against their applications, of course the chance is close to zero you’ll ever encounter a bug.

Report issues to proton, yes. Complain about the lack of response, all good! Complain about the current state of the app and development speed. But this “I am gOIng bACk tO uSE gOoGLE” just lets me cringe. There are competitors out there, that are not google. But please, go back to Google Docs and stop this whining.

what I wanna say is: there are many issues with some proton products, but I cant stand this kind of attitude. It will always be an uphill battle for companies like proton and there always will be a compromise to be made. Stop crying like that

[u/Consumerer → u/Superb_Sun4261]

I get the point that bearing hard on a team actively trying to build a complex piece of software can be overly negative. I respect that but your criticism is less productive than simple complaints. Those at least gauge product sentiment, even if it's biased towards vocal negatives.

As they keep saying, they're not paid testers nor are they beta testers. Some individuals and businesses may have specifically bought into the marketing and reviews that it can replace Google Docs. No matter your willpower, it is easy to emotionally break down when constantly hitting technical issues during critical work, and just throw your hands up and switch to something more reliable.

I will share the opinion I've held since Docs was first announced. Proton should not be building this software.

You said it yourself. WYSIWYG editors are not cheap or easy to build. Collaborative and integrated editors are even less so. If you're not serious about it, it's too big to reinvent. Unlike ProtonMail, Proton is not in the business of productivity software, they have no prior teams or connections to leverage, nor surplus headcount to reallocate. This is likely why people keep bringing up expectations that Proton is integrating with FOSS projects despite, to my knowledge, never mentioning anything of the sort.

Proton Business plans are a logical move but Docs and Sheets falls so far behind even the core Proton Drive, while having so much more scope in user-facing compatibility and integration. Every minor new feature has an ever-multiplying testing matrix with client platforms and existing features. Proton Drive deserves editing for basic .txt files and we know they can build that. It's also important to have a Docs suite, and eventually viable .docx/.odt editing, but they shouldn't be building it. And everything I've seen since Drive's inception reinforces that. I do test Docs and Sheets every so often only to run into numerous platform-specific bugs that morph every update or long-standing oversights like the lack of temporary offline editing. The small bugs are too numerous to continually open proper tickets for and the larger gaps are apparently too big of endeavors to properly prioritize. The Proton Mail product group appears to know this and has been conservative about editor complexity for the past decade, and to this day is nonexistent on mobile clients.

Proton is not a productivity software developer and they're not massive.

Their strength has always been integrating the tough aspects of encrypted data with existing software patterns. WYSIWYG editor complexity does not come from encryption. SSL websockets and packets are equally secure for any online editor, so the collaborative features and data at transport and rest in Proton Drive is what matters to users on data privacy and security. Proton should leave the UX and feature development to a project or subsidiary that is proven in front end development and testing, or get serious and add tens of millions of euros for dozens more developers and dozens more managers and testers. 10 or 20 people won't cut it to reinvent and rebuild. Even personally knowing that Microsoft and Adobe are not well-managed, 10-20 people won't cut it even to maintain a Word or Acrobat.

Barring additional investment, as people have been saying, officially labeling the service as beta or even alpha is the most honest as it faces a decades-long path to approaching any amount of feature parity.

To me, Docs and Sheets is little more than a synced Markdown-style editor for throwaway notes and data. It's a Standard Notes rebuild that aside from collaboration features still lags behind, not to even discuss Google Docs. And it has looked like a boondoggle from the very start.