Showing posts with label app. Show all posts
Showing posts with label app. Show all posts

21 July 2017

Stupid and Pointless 500 Index

This is a customer review on the Apple iTunes store for Meshlab's iOS application. Meshlab is described thusly: 
MeshLab for iOS is an advanced 3D model viewer. MeshLab for iOS has been designed to be able to display complex 3D models in a simple and intuitive way, allowing the accurate inspection of a 3D model through a precise yet straightforward navigation. 

I've used the desktop version of Meshlab off and on for a few months, and it's pretty handy. I was looking to get the iPad version so if I wanted to show off a model before printing it, I'd have options beyond e-mail, flash drives, or Dropbox
"When you open the game,"
It's not a game, it's a productivity app. It's a minor point, and I'm sure he meant to say "app", but it helps establish a pattern that's worth noting.
"there are a few models to choose from. It wouldn't let me change or edit them in any way besides changing the light effect. There wasn't a color button a shape button, nothing!"
This is almost a fair point, as the desktop version does allow you to paint the imported models, albeit crudely and with some questionable export settings. As for the shapes button, once again we're back to the main issue that this program is a viewer. It is not full-fledged modeling software. It never proclaims to be anything more than that, thus setting expectations by which it should be judged. Does it perform as advertised? If not, then that's a bad product. If it does, then it's ample, serviceable, adequate... etc.. If it has features beyond those advertised that are competently executed, then that's a fantastic app. If I expected you to fly by flapping your arms while thinking happy thoughts, would that make my criticism that you are a worthless person no one should ever have to deal with valid? 
"So I tried deleting all the models to see if i would then be able to create a new one. Nope."
You didn't try looking on the website or finding any information on how to use the app? You didn't think to look in the app's Help menu to see if the feature was even available? What makes more sense from a design perspective, hide the "new" button until all documents are deleted (especially considering there are only 4 default models in a drop-down menu that goes all the way to the bottom of the screen), or keep the button visible but display an error message that there is not enough room? Imagine if the fuel gauge of a car disappeared until the needle approached empty. 
"I couldn't even do anything because I didn't have any models to edit. There wasn't a plus button to make a new model."
A typical setup for a VIEWER. 
"so that basically made the app useless!"
As useless as a bicycle is for climbing Mt. Everest... As useless as a Jeep is for entering a low earth orbit... As useless as a can opener is for removing a computer virus... as useless as wishful thinking is for overturning DNA evidence... 
"Look, I'm not an app inventor."
Indeed.
"And I'm sure it's harder than it may seem. But seriously! You can do better than this!"
Yes, there are tablet-friendly 3D modeling programs out there, though their numbers are significantly fewer since Autodesk axed the better part of the 123D repertoire, but that doesn't change the fact that Meshlab is a VIEWER and not an EDITOR. 

I know I'm likely blowing this out of proportion; the app is doing well and this little one-star diatribe isn't going to hurt that for an instant. Also, it's certainly not as big a display of ignorance is the yahoo from a few months back who paid ten dollars for the SketchUP Viewer app ("viewer" is in the name) and complained that he couldn't edit anything. 

28 September 2016

Goodbye Cheetah Mobile

Many years ago, I learned the hard way the dangers of not having backups for sensitive data. I also learned that computers need maintenance on both the hardware side of things and the software side. For the few years I had a full-fledged Windows PC, there was no one I trusted more than IOLO's System Mechanic. Later on, when I moved to Linux, that was no longer a viable option. I still keep an account with IOLO open for the sake of my roommate and a very good friend who still use PCs (the license covers multiple installations). IOLO uses an annual subscription model, frequently with promos and discounts that make the whole operation all the more "set and forget". 
When I got my XPeria, I was surprised IOLO didn't have a stronger mobile presence to compete with McAffe and TrendMicro. What I came across instead was CM Security, short for Cheetah Mobile. My experience with them has quickly shrank from mostly favorable to downright annoying. 
I'll save my current stance on the subject of blocking ads for another entry, but I will give a small sample here. I understand that ad-support is sometimes necessary to maintain a business model. I don't mind pay-walls for added features. What I absolutely can't understand is making the ad-support option compulsory. CM is by and large free to use. I get ads on my phone, which I was okay with. However, the ads got out of hand, showing up at every corner, in front of every feature, and the worst part was I had no way out of it. Yes, CM was expanding its features, meaning more revenue required, meaning more ads. Here is my problem: there's no option for me besides walking away. 
I don't mind paying for apps. 
I don't mind paying regularly for apps. 
I have a rule against spending real money on Free-to-Play games, but something like an anti-virus or a CPU cooler or a junk organizer is a completely different kettle of fish. Those are useful. Those need constant updating. Those need regular support. 

I am completely and utterly content to pay to keep my phone optimized. 

Cheetah Mobile, however, did not give me any option to pay them. 

As such, I'm using someone else now. I won't say who on the off-chance they turn out worse, but so far they seem far more willing to give me options than CM

06 October 2015

Reverse Cryptomnesia?

Also, an inadvertent monograph on the Quinnspiracy and TvW at the UN because that's what happens when you get into a flow talking about programming... 

I talked years ago about the embarrassment of coming up with an idea only to find not only does it already exist, but it's so immensely commonplace and ubiquitous in your own life that it probably took more mental energy to forget it exists than for you to come up with it. This is putting a twist on that idea. 
I don't know programming. I don't know programming at all. I understand some of the ideas around it, but the leap from text in C++ to HD graphics is almost abstract for me. I've tried writing text adventures, but HTML is about the best I can do, and Depression Quest* is pretty much the kind of game I would want to create, though not nearly as pro-social or insightful... or worth playing. 
At one point, after hearing about all the various tools available, I had an idea to use one of these drag-and-drop interfaces to put together the laziest, most bare minimum "Hello, World"-shaming programs and then charge an absurd amount of money for it. Of course, I'm not saying I'm any kind of genius, much less that there's anything more than petty and opportunistic about such a venture, but I figure it's like snuff films; just because the idea is simple and plausible enough doesn't mean anyone's taken it all the way to reality. I know there's a proper name or attribution to the notion of, "if you've imagined it, someone else has likely made it" a more Zen-like perspective on the patent joke "anything that could be invented already has been". As for my "invention": 
Even the most expensive Android app, which is capped at 200USD (but is available as a six app set), is at least a set of desktop themes. I wouldn't call that essential, but at least the developer has enough skill to not look like a shameless opportunist. Meanwhile, one of the most expensive apps on Windows phones is only a mere half-step above the app that I would create. Mine would even be called "the 1000 dollar app that does nothing" (this was before I found out about the price cap) along with a myriad of disclaimers in the description that this is literally a kind of half-hearted social experiment/get-rich-quick scheme. My thinking was that, by the law of averages, I have the power someone would buy it just to burn money and have the dubious honor of having spent a ludicrous amount on a frivolity. 

*For the record, I have no problem with Zoe Quinn. I think the controversy around her has been absurdly blown out of proportion. It did turn my stomach a bit to see her alongside Anita Sarkeesian at the United Nations. As I've said about Sarkeesian, and as much as I legitimately like some of her videos such as the Lego one and even Ms. Male Character, she completely lost my respect with the Women as Background videos with their embarrassingly transparent misrepresentations of the games in question on top of the absurd premise of connecting real-world behaviors to in-game violence. Put simply, she's the worst person to champion her own cause, and while she certainly does not deserve death threats, I feel as though her issues overshadow Quinn's, who has been the victim of a massive, coordinated cyber attack and been accused of attempting to profit from the suicide of Robin Williams. To make matters worse, while I may not care about her personal life, the fact that there are so few women in the games industry does put her in an awkward position where her every inconsequential action carries absolutely onerous consequences. She shouldn't have to be an example, yet I don't think her position is discussed nearly enough. 

I guess you could say the reason I care more about Quinn than Sarkeesian is that Quinn is making legitimate efforts to enact changes in the games industry, blazing trails between the paths less-traveled while Sarkeesian is a bloody backseat driver. 

To put another way: 

If a film critic and a filmmaker were drowning and I could only save one of them... Well, I like The Island and even Age of Extinction had its moments. Sorry, Leonard. 

Final note: double-checking the definition of monograph to make sure I was using it right (you tell me), led me to this site which seems pretty damn awesome at first impression. 

22 June 2014

Oh, Twitter...

I love Twitter, flaws and all. I don't think it's the greatest site ever made, but it's easily in my Top 5. Lately, though, I've been having a bit of a rough time with it. 
My Xperia Z Ultra has been great, even if I'm only using it as a tablet as my contract with Verizon won't run out for at least another month. To ease the transition, I culled a number of apps from my old phone, the HTC Rhyme. It had been getting a bit bloated, and many of those apps work far better on the Ultra. One of the apps I removed early on was Twitter. Technically, I still have it on the Rhyme, it's simply not the full version, but HTC's dashboard version, Peep. Peep works fine and dandy, but I didn't realize how stripped down it was compared to its big brother. 
I access Twitter primarily through Tweetdeck. It has its own separate login and account settings apart from my Twitter account proper. As for logging in to Twitter, I'd recently upped the security on it in light of some recent bouts with identity theft and set up mobile notifications. If I log in to Twitter from any new place, I have to enter a code that gets sent to my phone as a text message. 
What I didn't know until now was that when I removed Twitter from my Rhyme, I kept it from receiving those login codes. I figured that since they were only text messages, whether or not the app was present was totally irrelevant. Now, if I try to log in to Twitter through my browser (or especially the Z Ultra) I can't because I don't receive codes anymore. The solution seemed simple: put Twitter back on the Rhyme and get the codes. 

Guess what I have to put in when I open Twitter on the Rhyme. 

It's actually an easy fix, simply a matter of finding another way to log in, but it's so absurd that it's set up in this manner. I'm entering a phone number, not a MAC address, so why does the app need to be present in order to get a text message? What if I didn't have a smartphone, but an old flip phone (or "feature phones" as T-Mobile calls them, or "dumbphones" as everyone else calls them), like if I had to move my SIM card to another phone because of damage? What if the app got corrupted and needed to be reinstalled? For all intents and purposes, that's exactly what's happening now. 
There's nothing more frustrating than a security measure that works too well. It's like when your kid beats up the school bully: You want to give them a high five for kicking ass and not taking any crap, but you want to scold them as much for fighting fire with fire. 

08 December 2013

Stumblrbum's Photo Finish

Tumblr's attempts to make posting photos via their mobile app have more or less all gone to pot. At least, that's been my experience of late. To be fair, it's good that they're trying to make it so you can post sets of photos instead of one at a time. Unfortunately, this simply doesn't work efficiently enough, and when your update is less efficient than spamming single photo posts, you really need to rethink your design schemes.

Recap: it used to be that after I took a photo, I could go into the "share" menu and select "Tumblr" from a list of sites. This would take me to a menu within Tumblr's mobile app to create a photo post, complete with tags and tweet settings. It was all very handy apart from not being able to post photosets.

Now, it's completely reversed. I have to go into Tumblr, select the photo post option, and then be taken to a menu where I can pick the photo from my gallery via thumbnails (more on that later) or go into my camera and take a new photo then. First problem, apart from this being very tedious and rather greedy on Tumblr's part by making "timed exclusives" of my photos, is that I can't access all of my camera's options, like exposure and effects filters. Couple that with the fact that I now have to open one application and make at least two selections in order to open another app which otherwise can start up almost instantly, and this is a really bad start. Second, I noticed that the photos I posted this way had a kind of checker board artifact pattern over them, like an old TV with the RCA cable coming loose. When your 21st century digital imaging system looks like a CRT monitor with flimsy composite connections by default, something's gone fundamentally wrong somewhere very far back in your process.

When something works just fine before an update, that's not a hardware failure, that's a limitation. What makes it really awful is that my phone is middle-of-the-road as far as tech specs go, so your update has potentially cut off about two-thirds of your users. Hell, I've heard from people with better phones than mine that they can't post photos at all, now or before.

Now, I have a good idea what your two cents on the issue is, "Look, you're overthinking this. Just do what you did before. Take the photo, then go into the app and post it then. You said yourself you can see your gallery as a grid of thumbnails to choose from."

Problem the third: Not every photo shows up in that grid, and which ones do and don't at any time is completely random.

Remember that episode of The Simpsons where Burns and Smithers walk through layer-upon-layer of security checks to get to a master kill switch for the power plant, only to find that said room has a rickety screen door that's nearly fallen off its hinges as another entrance? At least there you get to the same room and everything is there that should be because the console is bolted to the floor. There are more reliable ways to get to Narnia than my own damn photos. I'm really not kidding when I say that certain photos I take will not show up in this menu until days later, if at all. This app is in my phone. It literally has access to all my files on that device. I have to give it permission to do this when first installed. It's designed to be invasive, and it can't even do that. When FOX NEWS has a more complete picture of a story than you, it's time to rethink every decision in your life, ever, and when you've reduced me to making FOX NEWS jokes to analogize your incompetence, then you've really screwed up.

Speaking of grabbing at straws and not getting the full picture, today was kinda the last straw. I'm sitting in a Steak 'n' Shake, drinking coffee, eating a cinnamon roll, and making sketches in a notebook, as I'm wont to do at least once a week. Another part of this ritual is taking a photo of my setup, a spontaneous still life. Think of it as a kind of creative litmus test; if I can make coffee and pastry look interesting, I must be doing something right. Anyway, I go into Tumblr to post the photo, going through the menu to get to the camera app that otherwise starts up instantly and taking the photo. Normally, after all that, I get the menu where I can add a caption, tags, and all that other stuff before posting fairly quickly to my dashboard. This time, however, I get an error message that it could not save my photo and to try again later.

This is the equivalent of taking the photo out of my hands, throwing it in the cluttered mess of other photos which haven't simply gone missing, and saying, "Maybe it'll show up later."

The sole redeeming factor in this debacle is that while Tumblr lost my photo, my phone didn't. I could see it in my gallery right away (my gallery, not Tumblr's slapdash interpretation of it) and now, several hours later and using the full version of Tumblr, I can post it here by way of my DropBox, which the photo was auto-saved to within minutes of being taken.



And here's another I took without using Tumblr's increasingly lackluster interface (notice the effects filter):



So, what does this mean? Well, it simply means that my more spontaneous uploads of photos will be posted to Twitter instead of Tumblr (and then Twitter because of auto-share). If I end up taking a lot of photos of something, like stages of a cooking project or something, I'll post them here as a set. Granted, it's entirely possible Tumblr will fix this issue in future updates. However, given that it's made two since I started having this problem, I'm not optimistic anymore. At least now, though, it doesn't crash when I try to read notes on posts. 

10 December 2012

Twitpic Is An Apt Name

My phone has been having fits lately, mostly over the number of apps that I have installed to the memory card as opposed to the internal memory. Here's the problem, the internal memory of my phone doubles as the RAM. Most smartphones, going all the way back to the SDA I had, which was an old-school Windows Mobile phone, had a task manager where you could turn off anything that was running if it didn't already have an exit button programmed into it.
Anyway, the problem lately has been that the phone will claim it can't find the memory card, meaning even my photos can't be seen. As you might imagine, this really irked me in the worst way. Eventually, it would just sort of "fix itself" if I gave it time, at worst just restarting the phone. To be fair, I am a bit rough with my phone, but in my defense, its entire design scheme is built around never turning it off. The HTC Rhyme has a number of quirky little features and accessories that really endeared me to it when I started up my new cell service. One of these items of interest is a charging dock that turns the phone into a kind of desk clock. In fact, it's my primary alarm clock that I wake up to for workdays. The issue with this is that I have to set aside time in the day to allow the phone to die, to run completely out of juice and essentially "let it rest" for a while.
The trouble lately is that it doesn't seem to be enough, and it continues to give me grief over not being able to see the memory card as well as not being able to run certain applications if they're installed to the memory card. I would be browsing sites or checking messages when suddenly I'd get an error message that some app I'm not even really using has "encountered an error" presenting me with the choices of "report" or "force close." It got to the point where I stopped getting eBay notifications because it couldn't really run the app anymore.
As a result, I tried to do a little bit of housekeeping today, going through all my apps, clearing caches and moving them onto the memory card or erasing them altogether if I could, while leaving some apps on the internal memory (apart from the ones that are "locked" and can't be deleted for various reasons), namely Evernote, as it's sort of been my best (non-human) friend on my current writing project. One casualty of this venture has been Twitpic, which is only in a non-working state because it doesn't seem to recognize my account information. I mean, I know I'm entering the right password, but it's not recognizing it. Granted, I'm probably putting in the wrong password regardless of my confidence to the contrary, but I've really just given up on it. Twitpic used to be a place where I posted sketches and work-in-progress photos of art projects I would later post to DeviantART. It was kind of a "behind-the-scenes/coming attractions" sort of exercise, showing a glimpse into my admittedly unremarkable process. I haven't used it much of late as I've been writing, but even when I have made a few drawings or notes, I don't really miss posting the images.
Who knows, maybe I'll join the rest of civilization and just start using Instagram?

Doubtful, but I do have a short essay in mind about Instagram, and the often ludicrous level of popularity surrounding it. In a way, it's kind of like how I felt about Twitter: in theory, it's genius, a kind of "bad by design" camera in line with Lomography or other classic experimental photo techniques. In reality, it's earned a rather unfavorable nickname, something like "Hipster's Polaroid." There's a tweet I found once that's a reply to Nikon regarding their Android camera that came out some months back. If I can find it, I'll write the essay then.

In the meantime, short summation of events:
Phone is wonky.
Writing project is going very well, for better or for worse.
Twitpic has packed up.
Evernote is my best friend.
I'm considering getting an eBook reader, but I'm debating about a color scheme, and the only place I can post a poll about it is on DeviantART, which would mean bumping down a poll that's relevant to my current project.
Current random object of fascination: Book straps.

06 August 2010

Because I'm an Audiolog Fanatic

Since moving into a new place where we actually get a cell signal, I've been shopping around for a new phone as well as a new carrier. I was looking in the AT&T store and found myself trying out an iPhone. It's not the first time I tried one, but I only felt compelled to give it another go because I was waiting for a sales rep to finish with another customer. Without this turning into an anti-mac rant, I'll sum up my sentiments toward Apple in a single sentence: I've always maintained that Apple is a fitting name for the company because if there's one thing it excels at above all, it's polish.
Anyway...
I tried out the voice recorder application, the default one that comes with the device, as opposed to a third-party one like Night Recorder (which is actually kind of cute), so I wasn't expecting anything beyond what my current phone has. The interface consisted of an image of an old studio microphone, complete with a VU meter. On other side of the meter were two buttons, one for recording and pausing, the other to stop. When I first tried to make a recording, I wondered if the needle on the VU meter would move along with my voice. It didn't, but here's the part I don't get: when I tap the screen, the needle jumps.

The programmer made the VU meter touch-sensitive, but not sound-sensitive.

Why?

I mean, sure, the "Oscilloscope" image that appears on my phone when I press record is just a looped animation, but at least it only plays when I press record; it's not linked to another function or other part of the interface. However, making the VU meter only respond to tapping really just made me think at first that I wasn't being loud enough to get a rise out of the needle, which was preposterous given the noise level of the store in general.

It just strikes me as bad programming (not lazy programming, wherein the needle wouldn't have done anything at all) to go to the length of programming a VU meter's needle to respond to tapping a microphone (an image of a microphone, but one nonetheless) but be unaffected by the sound said "microphone" would hear.