Near the bottom of the lite.twitter.com page it states "Twitter Lite...developed in partnership with Google." Is this the beginning of a partnership test with google as a sort of test to see how viable twitter would be to be acquired by google? Sort of like a few first dates before considering "corporate marriage"? Hmmm...perhaps my conspiracy theorist cap is on too tight. I wouldn't say that I'm a fan of either of t…
Introducing Twitter Lite
111–120 of 165 posts
Re: Introducing Twitter Lite
#112Earlier quoted context omitted.
I think they used React Native for Web https://github.com/necolas/react-native-web
Wait what. A web framework, adapted to work for native mobile, adapted back to work on the web?
Re: Introducing Twitter Lite
#113When twitter stated it ran via SMS, that was twitter as about as lite as you can get data wise. SO in effect they created a problem to promote a solution that is still short of what they had originally. Now I understand they need to make money but I personally find the promoted tweets they offer do seem to miss the target and are in need of some refinements in who they promote towards. I find it rare to find a promot…
An HTML interface is worse than SMS? Please, lets not pretend Twitter is worse with a richer interface with amazing features such as links and images.
As for the rest of your assertions, that is entirely a different matter and not one I raised in the slightest.
Re: Introducing Twitter Lite
#114Re: Introducing Twitter Lite
#115Re: Introducing Twitter Lite
#116Earlier quoted context omitted.
This comment is getting downvoted but if it's true, it's absolutely a good point. They are optimizing for what is inherently slower: loading JS in the client before anything can be seen or interacted with, rather than rendering HTML and forms so one doesn't have to wait for JS to compile and execute (and all the tracking bloat that comes with it).
It is not true, the slow part of web applications is loading over the network, server side rendering puts a dependency on the network and is therefore vastly slower. With service workers and client side storage you can get to display at least a shell, sometimes the entire UI without touching the network. It is a lot faster
Service workers are a cache (and background process), and you still have to consider cache misses. Even if you have a giant JS app and cache it, users still have to download all the JS to actually work offline no matter what.
Re: Introducing Twitter Lite
#117This is much better then the bloated main UI. But I'd wish an option for an even lighter HN like interface. It still doesn't look to good in a text browser like elinks. One or 2 lines per tweet max would be ideal. That and a rss/atom feed that can be fed into the matrix network and clients. Originally it was a listing of 140c messages, ideal to quickly view the status of your friends to enhance social proprioception.…
They've got bills to pay. Something's gotta give. Are you willing to pay to use Twitter?
Re: Introducing Twitter Lite
#118If you like this, you should look up Facebook Lite and Messenger Lite. My phone runs so much better after switching to those.
"This item isn't available in your country." That's disappointing. I should be able to choose Facebook Lite if I feel like it'd be a better experience for me.
Re: Introducing Twitter Lite
#119Re: Introducing Twitter Lite
#120Lightweight is awesome. I feel that the absolute most important next improvement is in managing spam and fake accounts. Things like Lite keep me from deleting my account. But with less spam, I'd probably use my account.
I don't deal with spam much, I notice the occasional fav or retweet from obviously fake accounts, sometimes I get a mention too. But all of these happen once per month maybe and I do my job in blocking and reporting every account I notice. Once per month is a pretty low rate, I get more spam than that in my email Inbox. I also have direct messages from everybody active. Since enabling it I haven't received any spam.…