TMA
Active member
Exactly. PWA might not be the right direction for apps yet.
Exactly. PWA might not be the right direction for apps yet.
...and Apple is aggressively pushing app services and customers off their app store.I know about how aggressively Google is pushing progressive apps...
When Safari service workers hit live, PWAs will be the only solution, except for those who can afford to develop their own apps.PWA might be good 2 years from now but it's not a viable solution right now.
Saying that it will be the *only* solution is a bit of an exaggeration. We will see how this rolls out....and Apple is aggressively pushing app services and customers off their app store.
When Safari service workers hit live, PWAs will be the only solution, except for those who can afford to develop their own apps.
A bit of an exaggeration how? Apple 1. implemented push notifications on macOS (top-priority PWA feature for iOS), 2. started developing service workers for PWAs (which is necessary for iOS push notifications, unlike macOS), and 3. as you quoted set a deadline to take down app services.Saying that it will be the *only* solution is a bit of an exaggeration. We will see how this rolls out.
Read the entire article I posted. App had push notifications on MacOS since OSX Lion. I guess that was 4-5 years ago and I've only now started seeing major sites adopting it. PWA may be way to go but in 2 years time the needles aren't shifting.A bit of an exaggeration how? There are native apps, progressive web apps, and what? Apple 1. implemented push notifications on macOS (top-priority PWA feature for iOS), 2. started developing service workers for PWAs, and as you quoted set a deadline to take down app services.
Read it in it's entirety yourself. iOS had push notifications since 2009 (8 years ago), and macOS had push notifications since Mavericks, you are thinking of local (not push) notifications. There are native apps and PWAs which are coming soon to iOS, there is nothing else.Read the entire article I posted. App had push notifications on MacOS since OSX Lion. I guess that was 4-5 years ago and I've only now started seeing major sites adopting it. PWA may be way to go but in 2 years time the needles aren't shifting.
The thing is that they won't be affected, stop scaring people unnecessarily.Read it in it's entirety yourself. iOS had push notifications since 2009 (8 years ago), and macOS had push notifications since Mavericks, you are thinking of local (not push) notifications. There are native apps and PWAs which are coming soon to iOS, there is nothing else.
Will affected customers go 2 years without a mobile presence? That is an exaggeration.
We'll see after Apple gets through their holiday submission backlog in JanuaryThe thing is that they won't be affected, stop scaring people unnecessarily.
We have deployed a LOT of apps and we have got 3 apps approved this week and 1 was yesterday. Will keep this thread updated, but I can't foresee anything major for us.We'll see after Apple gets through their holiday submission backlog in January
We initially wanted it to be out this Monday after beta testing but we haven’t achieved feature parity with the existing app yet and we don’t feel it is ready to be released yet.
YesThanks for the quick update. I assume this implies you're 'close' i.e. few weeks away at most?
Essentially they are saying give your customers the source code and make them do the publishing work, or build a shared app like TT. I don't know what this has to do with spam, but it's clear they are deliberately pushing app services off the store (why...?).4.2.6 Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app’s content. These services should not submit apps on behalf of their clients and should offer tools that let their clients create customized, innovative apps that provide unique customer experiences.
Another acceptable option for template providers is to create a single binary to host all client content in an aggregated or “picker” model, for example as a restaurant finder app with separate customized entries or pages for each client restaurant, or as an event app with separate entries for each client event.
Instead, Apple wants every app on the App Store to be published by the business or organization behind the app. (This is something that’s been suggested before). That means your local pizza shop, your church, your gym, etc. needs to have reviewed the App Store documentation and licensing agreement themselves, and more actively participate in the app publishing process.
Apple in early 2018 will waive the $99 developer fee for all government and nonprofits starting in the U.S. to make this transition easier.
This is opposite of what they are saying. Looks like @turnkeymobileapps is twisting the words and trying to confuse people into believing something that isn't true.Interesting news... (update)
Essentially they are saying give your customers the source code and make them do the publishing work, or build a shared app like TT. I don't know what this has to do with spam, but it's clear they are deliberately pushing app services off the store (why...?).
Source: https://www.washingtonpost.com/news...lled-thousands-of-apps-from-small-businesses/The changes to the policy allow companies like ChowNow to operate — but will require a little more work on its part. Namely, it will have to have create accounts in the App Store for each of its clients.
It's expected right now.is it expected that:
p.s. I'm trying the app with on RPNation.
- is not possible to "pinch to zoom" on posted images through the app?
- is not possible to choose prefixes during the thread creation?
- is not possible to choose existing tags as in the browser?
- there's no search feature
We use essential cookies to make this site work, and optional cookies to enhance your experience.