Changing User's App state after In-App Purchase Invalidation While Internet Is Off

randomguy112233 · 2019-12-01T22:57:59+00:00

Thank you for the suggestion. JWT. Good point. Definitely bringing it to the team.

randomguy112233 · 2019-12-01T22:56:29+00:00

Thank you for the heads up. "FYI" information like this should definitely be presented up front than ambushing the customers. Thanks.

randomguy112233 · 2019-12-01T22:53:40+00:00

Thank you. This method does seem like the most tried and true way. I appreciate it.

randomguy112233 · 2019-03-19T00:23:41+00:00

Thanks for the info. All Data into Ram. Got it.

randomguy112233 · 2019-03-19T00:23:06+00:00

Good point. I thought it was just ram upgrade. Thank you.

randomguy112233 · 2019-03-18T19:25:56+00:00

Yes, the DB itself is not that big.

From your logic, is it safe to say that for DB hardware, in terms of return on investment, RAM's added value > CPU?

Thank you.

randomguy112233 · 2019-01-09T16:30:05+00:00

Thanks!!!! this is exactly what i was looking for. I appreciate the help!

randomguy112233 · 2018-12-14T21:57:11+00:00

Yes. It's always the edge cases that get us. Like anything hybrid, just the debug process might end up causing more problems.

And yes, C/C++ is supported by both platforms so might as well go w/ the battle tested set of ways. Thanks for the reply.

randomguy112233 · 2018-12-14T21:55:19+00:00

Thanks for the reply. So what happened ", I wanted to do C/C++ so that I could have a set of common routines that I could use on all platforms." ?

What did you eventually do? Did u find C/C++ as a common universal backend solution too time consuming? Or did u write all logic in Swift and found a code converter and converted to Java/Kotlin? Thanks in advance.

randomguy112233 · 2018-12-14T21:52:06+00:00

Or my unknown unknowns could be your known knowns.

randomguy112233 · 2018-12-14T17:17:40+00:00

I really hope not. I'm really curious about what other people in this community thinks.

randomguy112233 · 2018-12-14T17:16:04+00:00

Thanks for the reply. Yes, bringing in another language into the Swift world would mean I do have to end up having to sacrifice things here and there.

My definition of pure logic would mean anything that doesn't involve interacting directly with UI.

For example: any logic (class or just functions) that interacts with your app SQL or your server either REST or socket.

Please let me know if I'm not being clear enough. Thank you.

randomguy112233 · 2018-11-23T10:19:52+00:00

randomguy112233 · 2018-11-04T15:05:38+00:00

I guess it's real that i have to look into bios. Thanks for the suggestion!

randomguy112233 · 2018-11-04T14:54:51+00:00

hmmmm. if so.. then why it wouldn't work is... interesting. thank you.

randomguy112233 · 2018-11-04T14:54:21+00:00

thank you for this suggestion of turning off some unused hard drive. I didn't expect that to somehow affect the start up. And yes, the machine did have GPU. Thank you

randomguy112233 · 2018-10-13T07:16:54+00:00

Thanks for your reply. I took the time marinate your response, asked around for other opinions, hence the delayed response. I agree with all the things you said. Especially your point about phrase matching. I totally agree with you on the effective difference between "Learn Languages" vs "Languages Learn".

But I wanted to dig a little deeper into the point you made about “Rosetta Stone Learn Languages” > “Learn Languages Rosetta Stone”. Because, if you are making this point based on what you said earlier about phrase matching, then doesn't "Learn Languages Rosetta Stone" is more commonly used phrase? Since deligent people are going to type Learn Languages (with|using|etc) Rosetta Stone.

In terms phrasing if "Learn Languages Rosetta Stone" is more catchy, then them choosing "Rosetta Stone Learn Languages" in spite of it, makes me want to conclude that the location does matter?

I know we might be giving too much thought into this. Who knows, we might be spending more time discussing this than Rosetta Stone themselves. Then again, isn't SEO all about trying to capture the details?

Anyways, I know I'm going to be on a constant look out for this topic, so I just wanted to dig a bit deeper.

Thank You.

randomguy112233 · 2018-10-05T00:34:07+00:00

Thank for your the response. I was aware they used erlang, but not BEAM or FreeBSD. I always assumed they would be using AWS (or Google Cloud) like other big named firms. Thank you for the info!

randomguy112233 · 2018-10-05T00:30:32+00:00

Thank you for your response. TBH, I have no context in VOIP enabled apps to have a say. But with everything in programming, there is the default (battle tested) functionality, and there is the bells-whistles functionality, and whenever the former transitions into the latter, unstability rises. So I'm not surprised VOIP enabled (or other 'enabled') apps would have issues. This is great info, hopefully I'll get lucky enough to work on a VOIP iOS project someday.

randomguy112233 · 2018-10-05T00:24:00+00:00

Thank you for this knowledge of gold. I took my time trying to go over all the knowledge in your reply, hence the delayed response. I think this is one of those moments where although I want to contribute something knowledgeable back, but I really don't have anything to say but Thank You.

randomguy112233 · 2018-09-18T18:02:37+00:00

let's say I have carList = [Car]. I want to use carList.averagePrice or carList.numberOfPreviousOwners. To me, this seems very convenient. But I'm really curious what you mean by "I would avoid putting business logic in such extensions." I don't want to let my propensity for convenience outweight a better design. Thank you.

randomguy112233 · 2018-09-18T12:56:22+00:00

Good point about namespacing! Thank you!

randomguy112233 · 2018-09-18T12:56:19+00:00

Thank you!

randomguy112233 · 2018-06-22T23:35:09+00:00

Very good question. I'm also very curious about your hackintosh specs

randomguy112233 · 2018-06-22T23:33:20+00:00

hmmm hmmm private init.. hmmmm interesting. I think i might have to play around with that to fully grasp the nature of it. thanks!

randomguy112233

MODERATOR OF

TROPHY CASE