Pixel 5 is "small" in android parlance, but still bigger than the Pixel 4a for instance, which is already slightly bigger than the SE.
I think parent could have been fine with a Pixel 4a if it wasn't for it starting to age (using the lastest OS on it, feels definitely slower at times , especially when starting the camera which is a bummer)
I was adding info on how app use in it is when the edit-window closed...
Most apps are actually fine, if a bit cramped. The exception is dialogs. I usually have to scroll to see all options. You get used to it, but it isn't great.
Webpages are alright, but I do occasionally need to hide the keyboard while filling out forms to see feedback provided below the input (e.g. username already taken, passwords don't match, invalid CC #).
I've never really gamed on my phones, so can't speak there.
The one thing I did with a larger phone that I don't do on my Jelly2 is read things like textbooks and comics where images and text need to be laid out like print. It's too small to fit a whole page of legible text and images at once. 720 horizontal pixels and a 5" screen is the minimum there IMO, though really this is what e-ink tablets were made for.
Does it run a non-Google/free OS? My primary qualm about switching to a budget Android phone from an iPhone is the security and privacy aspect, which seems okay under Apple but atrocious under Google/Android.
I think the Samsung Galaxy S10e and some of the Google Pixel models are nearly hand-size, but I don't know of any that rival the (now unsupported) Xperia XZ1 Compact. The XZ2 Compact is (AFAIK) still supported by LineageOS, but it's chunky.
I have read rumors that a new Xperia Compact model is likely within the next year. I don't want to get my hopes up too high, because this is unconfirmed and because the definition of "compact" seems to be expanding over the years, but I am optimistic.
I doubt that we'll ever see the likes of the Xperia Mini Pro again.
Nearly impossible, and I'm saying this as a lifetime Android user.
Your best bet would be boutique OEMs like Unihertz, who have a 3.1-inch Jelly phone (underpowered) and a Blackberry style Titan Pocket with a hardware keyboard and 4-inch screen.
Neither of these sound like what you want. In the Android world, one can only hope that another small-time OEM will swoop in to fill the gap, before inevitably disappearing.
Since pocketability is a large component of the size question, the foldable Motorola Android phone is worth taking looking at (if you can afford it). Unfolded it's modern-sized but folded up it fits in more places.
It's the other way around for me. Usability trumps everything. Trying to use my phone one-handed is extremely frustrating, even with a rear grip, and I have what is considered a "small" phone (Samsung Galaxy S10e).
I wish phones had thumb trackpads like BlackBerry phones had. The BlackBerry Classic (2014) had one and it worked incredibly well, even in Android apps, surprisingly (it works by moving the focus, not a mouse pointer, except in the browser, where the pointer means desktop mode is actually usable). Being able to reach the entire screen just by twitching your thumb a few millimetres is sadly probably never going to be possible again.
I used to use a Motorola phone I got off Amazon for like $200. It was great, but various factors have caused me to return to using an iPhone. Looking online a bit maybe it was the G7 plus?
My favorite "feature" of these Android phones is the price. It's like having insurance on your phone. If you lose or break it, it's not $1500 down the tubes.
> My favorite "feature" of these Android phones is the price
Honestly that's my favorite feature of iPhones too. I've always bought used iPhones 2-3 generations behind. And they're often supported for many years.
Current iPhone is 1st generation SE 2016, probably worth less than $80 and runs latest iOS.
I’ve usually bought 1-2 generations behind, often at the $250-400 price point, and then run them for 3-4 years or so. I just replaced the battery on my wife’s X and that looks like it’ll now go well past the 4 year mark.
Having spent a good amount of time looking at potential JavaScript malware that ended up being repackaged GTM, I'm pretty confident anyone who says they're "blocking Google Tag Manager" has their head in the sand.
Atleast in my country, to send legitimate marketing e-mails, a user has to be given a choice to opt-out *before* the first e-mail.
So it's not enough to allow them to opt-out with an e-mail exchange or an unsubscribe link, you must allow the user to opt out when you initially gather the contact information.
If that wasn't done, it's illegal (and unethical) to send marketing e-mails, even from a paid service.
> we don't want to track individuals - we just want to measure if the ads we paid for led to sales
well. if your goal isn't tracking individuals, then why are you attaching unique ID's (in cookies) to track individuals on your website?
And I'm not talking about third-party cookies disguised as first-party.
logglytrackingsession (lifetime: session)
notion_experiment_device_id (lifetime: 1 year)
Both are unique to a specific user and are used to identify a single individual. The first one is short-lived, but obviously meant for tracking and the second one can be used for tracking, identifies a single individual and is long-lived.
Yes like the peer reply said that's Notion, not us. But good point, another thing to keep in mind if you try to use the "Share to the web" notion feature.
My real point is, if you use a service to provide your own service, you give them your blessing to do whatever they want with your brand. This includes facebook and their tracking scripts.
Thus we need to audit what our service providers are doing and limit their impact once we've completed the evaluation, making sure they don't alter the deal later.
Also tracking ad conversions is as simple as using a unique parameter per campaign, when buying the add. Just append `?campaign=facebook_campaign-name_202202` to your link and that's enough to measure the ads effectiveness. No need to attach unique ID's to users, sessions etc... Aggregates keep the users anonymous and give you enough actionable insight.
While I agree with the sentiment of your first point, in practice if each small business were expected to audit every one of their inputs, it would be hard to get any business done.
As for your second point, yes, that is precisely what I referred to in my original post - that we could deal with the end of IDFA / that we just want to make sure ads are effective - SKAN which provides aggregated statistics is mostly ok for us.
> in practice if each small business were expected to audit every one of their inputs, it would be hard to get any business done.
While I agree, that a full audit would be difficult for smaller operations, it took me 2-5 minutes to do a quick check on what is being stored client-side and to come to a logical conclusion if individual users are being tracked or not.
It's a decision, one that you can (probably) make. For me, in the EU, it's no longer a choice and I personally think regulation(GDPR) was needed because, without it, no one took user-privacy seriously.
> As for your second point, yes, that is precisely what I referred to in my original post - that we could deal with the end of IDFA / that we just want to make sure ads are effective - SKAN which provides aggregated statistics is mostly ok for us.
GDPR would also apply here. If there's an option to process less data and achieve a similar result, one should use that option and using a more invasive method(identifying individuals) for tracking would be illegal. It's called "the data minimisation principle"
Yes, agree, we wanted to try it out for this because we like it for work and it was quick to write up and publish and we thought it might be more flexible for writing up documentation, linking, etc. But we are not satisfied either: Very slow to load, formatting is fiddly and imperfect. We will have to use something else.
this is just the first step. If the consent string wasn't PII, all the other data tied to the consent string would not be PII as well, because this is the cookie that brings all the data together.
So now that we have confirmed that they do indeed process PII and use the consent string as the unique identifier that ties the whole profile together we can start doing what you want. Going after the companies that attach other datasets to the consent string.
Before this ruling, the companies/controllers would have said that we process no personal data, thus GDPR doesn't apply. Now we have a ruling, saying that this is not a valid excuse.
"Before this ruling, the companies/controllers would have said that we process no personal data, thus GDPR doesn't apply."
That is not correct. These companies use TCF because the GDPR applies. If it did not - they would not have to use it. The GDPR automatically applies as soon as cookies come into play - regardless of what is in the TCF string.
The main thing here is not that PII data comes into play but that the IAB is the controller. Until now the controller was/is the website that actually controls (and passes to 3rd parties) user data. That is why you have to agree to joint controller agreements if you want to integrate the TCF frameworks on larger web sites.
Some background in IPs: The ruling mentions the reason TCF is PII because it can be combined with IP addresses. No one challenges IP addresses as PII data anymore. There were many ruling that classify IPs as PII - specifically in Germany (even pre GDPR).
Consent means offering individuals real choice and control. Genuine consent should put individuals in charge, build trust and engagement, and enhance your reputation.
Consent requires a positive opt-in. Don’t use pre-ticked boxes or any other method of default consent.
Keep your consent requests separate from other terms and conditions.
Be specific and ‘granular’ so that you get separate consent for separate things. Vague or blanket consent is not enough.
Be clear and concise.
Make it easy for people to withdraw consent and tell them how.
Avoid making consent to processing a precondition of a service.
Personalized analytics and tracking roll-out (including on-prem) was pulled back ~2 years ago[0], they're on another try[1] currently with a heavy-handed hiding approach. Including small additions to release notes[1], short lived and hard to find feedback threads[2] etc...
Including deleting/hiding tickets that get posted on HN[3][4] and contain plans/info that users might take negatively/provide negative feedback on.
PS: full disclosure, I've been an active opponent of these changes, as they are illegal in the EU and make it impossible to self-host the service while protecting our users privacy.
yeah, it's going to happen and someone else will come and win everyone over by acting nicely.
It's a cycle and I can confidently say, working in a company that has used the same approach to win customers over, it's really hard to keep the honest culture going.
> There's a reason (many? most?) people are jerks. Being a jerk works.
Yes, but I would argue that it only takes a few sociopaths to ruin an entire community, by exploiting trust, and doing other things that most other people wouldn't dream of doing.
You're not wrong. That doesn't mean it's going to change, however.
Might I recommend perusing "Meditations on Moloch"? It will both depress you (since you seem like a decent person) and give you a framework for why and how these things happen.
Also prompt departure of their VP of compliance after her concerns about discriminatory practices where dismissed/ignored in the open discussion thread.
It's actually very dependent on the country and jurisdiction.
Some EU countries require that you offer a simple and effective option to opt-out when gathering the contact details. Depending on the content, that can be a required to be an opt-in toggle.
It's not enough to offer users a way to unsubscribe once you've already started spamming them, there should be a way to not have the first spammy newsletter/newsletter group.
Currently, it seems like the iphone SE is alone in the segment?