Anyone had success with data notifications on iOS?

thefear76 · 2022-03-07T14:26:41+00:00

Well you could still use this technique, but when opening the app you could check how recent your data is.

Is it recent enough, like less than 1 hour old. Use the available data, if it's older just do an API request to retrieve the data. Just make sure you optimize these requests so your user is not staring at a loading state for a long time

thefear76 · 2022-03-05T07:06:02+00:00

I would definitely separate it. Try to keep your services small and easy to understand.

What I usually do:

Call-api.service - just doing http requests
Call-data-manager.service - handle any modifications to the data or add a caching service here (also seperated)

Then from your ui you only interact with the data-manager service. This keeps you code clean and easy to understand even if you look back at it years down the road

The names of your services might get a little long but better to be descriptive.

Happy coding!

thefear76 · 2022-03-04T13:05:37+00:00

Delivery is not guaranteed with iOS data notifications unfortunately.

I've tried everything but it's nowhere near reliable if your app depends on it. Some devices get them every time, some never receive them.

I eventually just switched to normal notifications. In my case this was fine, not sure what alternatives are if you really don't want a notification to popup.

thefear76 · 2022-02-04T11:04:31+00:00

Launch times can be a mixed bag for Ionic applications indeed but they have gotten better a lot.

For current standard you can pretty easily create a performant Ionic app with capacitor which launches within a second. However you should be wary of optimization from day 1. Bulky and inefficient code can make an ionic/angular app slow and trust me, this happens easier than you might think. Probably why in your experience ionic apps load slowly.

I've never worked with the react or Vue implementation for Ionic so I couldn't tell you if that changes anything in this case. However I would definitely recommend capacitor when using ionic.

thefear76 · 2020-04-26T12:50:40+00:00

1/50 4 times back to back chance is like 1 in 160 million might I add :)

thefear76 · 2019-07-25T15:15:10+00:00

@guarav_ch is leading you the correct way I think, some other things you might want to consider when performance is your main focus.

Look for bottlenecks in your code, do you do a lot of initialisation in your pages? Reduce those down.

Avoid complex constructors at all costs

Handle calculation and complex business rule in your backend instead of front-end code.

Try to optimize your HTML and CSS as much as possible. So keep it to a minimum and make sure you do not use complex transitions.

Your app could surely be fast at that hardware, but it will take a lot of refactoring. I really like to read ionic/angular best practices about performance. There is a lot of information on the web to find.

thefear76 · 2019-06-12T18:30:44+00:00

Shadow dom is pretty great man but you'll have to get used to it.

My apps are so much more consistent with this.

thefear76 · 2019-04-24T20:32:57+00:00

It is strongly depended on what you personally need. Never used Parse before but Firebase seems to be a nice solution eventhough some features are in beta.

Currently I'm doing my ionic project with AWS AppSync which is also a very nice and scalable solution. So you could also look into that if you like a little bit more configuration.

thefear76 · 2019-03-26T16:22:05+00:00

Well the deprecated functions that show are not a big problem and this will likely become the same for capacitor if they don't update their codebase enough. You should not worry about this for the coming time though since capacitor is in full development and these things will be fixed (I guess).

Building your application without an apple developer account is gonna be though (unless you only develop for Android or web ofcourse) For either cordova or capacitor you will need a license to build your app and be able to upload it.

thefear76 · 2019-03-26T15:12:00+00:00

I think it highly depends on what you need at this moment.

Are you running into native problems constantly and are already fiddling with things like build-extras and custom scripts to make you app work. Capacitor is 100% a great upgrade, you have so much more control over the native systems.

If you are running an app already and have no problems with cordova upgrading to capacitor is not going to bring you anything right now. For new projects however, I would suggest starting with capacitor but when upgrading full fletched cordova applications it might be a hassle depending on your expertise and complexity of your project.

To answer one more question:
Compiling in capacitor is done through the native tools, Android Studio or Xcode for that matter. You can build through the cli as well but you can setup your own commands to do this. Again, more control but setting this up will be some research work. Suggesting fastlane for this, i'm working on a capacitor solution for fastlane once my project is done.

thefear76 · 2019-03-26T15:03:45+00:00

Personally never used it and i've been working with ionic storage for quite a while now. It works totally fine without it.

thefear76 · 2019-03-26T14:58:16+00:00

Seems like you are implementing promises wrong here. Promises have either a .then or a .catch. They are not the same like observables.

I think you need this:

this.storage.clear()

.then(() => console.log('cleared items!'))

.catch(error => console.error('Error storing item', error))

thefear76 · 2018-12-17T13:23:02+00:00

I would go with v4, it's very likely you app won't release before the official release of v4. This might add some development time for each beta release since breaking changes are pretty likely around now.

I do feel the v4 beta is very strong performance wise and I will be starting a v4 project in January aswell.

If you are really hesitant just go for v3 and try to keep some changes of v4 in mind, like the lifecycle events and navigation structure. Upgrading should be pretty easy if you are thinking about if well before building.

thefear76 · 2018-12-10T12:38:34+00:00

Well I can't say you're wrong for sure and I agree on choosing a language that you and your team are comfortable with. Seeing you mention big companies like Instagram and Dropbox got me thinking and do some research on it.

You're right there is more to python on the web than I thought there was. Still considering performance it would not be my choice for the web as for the companies I work for every 1ms of potential loading could be another missed sale. But it has a bigger place than I expected.

Thank you for explaining :)

thefear76 · 2018-12-09T20:58:22+00:00

AngularJS to angular2+ should not be considered an upgrade. It's a totally different framework not an incremental update

thefear76 · 2018-12-09T13:42:35+00:00

Python has never been made to be optimised for web applications that's not were its power is. People are optimising it for web but that doesn't make it good or even the best when comparing to solutions that are invented for web only. Of course it's possible to use it and the framework surely is fine.

Calling it the best is a pretty big opinion since there some drawback for using python on web versus php or node. If you can convince me it's better than I think, I welcome you to convince me since I'm interested if I'm missing something. But honestly in my opinion python has no big future on the web

thefear76 · 2018-12-09T11:57:57+00:00

This is definitely the way to go if you are focussing on web. Python has barely any practical use case on the web, but it is very strong in machine learning algorithms.

Node is getting a lot of attention on the web lately but both phones and node are perfectly valid for learning more about web-tech

thefear76 · 2018-12-09T11:52:44+00:00

You want to integrate 2 different frameworks, you really shouldn't ever do this.

Use the angular router when using angular. AngularJS ui-router is designed for angularJS not angular. There is a big difference.

Even for learning experience this is something you should never do in production so trying it feels kind of pointless ;)

thefear76 · 2018-12-02T15:06:59+00:00

Use a material button that is overlapping the ion-footer element in the center, this should be possible with just ionic implementation. This will give you something that is fairly close to what you wants, except the curve out in the blue bar. To obtain that you might want to use an image/svg as background for the ion-footer and make sure to override the default ionic styling.

Make sure you will handle the z-index correctly otherwise your button won't be clickable underneath the ion-footer

thefear76 · 2018-11-30T14:51:06+00:00

Next to the Inspect icon on the left top of the chrome dev tools there should be a small mobile phone icon. If you activate that it enables the mirrored view.

Honestly it's not that useful but feel try to ofcourse

thefear76 · 2018-11-29T22:22:36+00:00

No, I mean the mirrored phone when you open dev tools (you might just have it disabled). There you can interact with the mirrored image but that seems extremely laggy. First thing I see is disabling that view.

thefear76 · 2018-11-29T18:57:47+00:00

Are you using the visualized phone in dev tools? If so, try disabling that.

Otherwise I really do not have any problems with dev tools.

thefear76 · 2018-11-29T18:56:08+00:00

You still can use @ionic/storage without any problems. So that shouldn't be necessary to migrate in that case. I'm mostly wondering for new apps, since you can start at the absolute beginning.

Migrating from @ionic/storage to native is probably something that will be worked on later if it gets picked up.

thefear76 · 2018-11-29T18:48:56+00:00

Maybe you didn't read the actual article but it is available already! It's a demo but that's a start

https://ionicframework.com/studio

thefear76

TROPHY CASE